Triple
T30014084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount of Tartas |
E762546
|
entity |
| Predicate | relatedTitleHouse |
P23794
|
FINISHED |
| Object | Lords of Albret |
E762545
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Lords of Albret | Statement: [Viscount of Tartas, relatedTitleHouse, Lords of Albret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTitleHouse Context triple: [Viscount of Tartas, relatedTitleHouse, Lords of Albret]
-
A.
usesTitleForHouses
Indicates that an entity applies or assigns a specific title or naming convention to houses.
-
B.
relatedTitleHolder
Indicates that one entity holds a title or position that is related or connected to the title or position held by another entity.
-
C.
titleHolderHouse
chosen
Indicates that a particular house or noble family holds or is associated with a specific title.
-
D.
estateLinkedToTitle
Indicates that a particular estate is legally or formally associated with a specific title.
-
E.
associatedHouse
Indicates a relationship where one entity is linked or connected to a particular house, typically as its related or corresponding house.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a01ed1790148190b08c1dba53de4371 |
completed | May 11, 2026, 2:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a272212fcdc8190944a379dd5a03967 |
completed | June 8, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_6a01e9c20798819085760b377dc7b3fa |
completed | May 11, 2026, 2:37 p.m. |
Created at: April 29, 2026, 6:45 p.m.