Triple
T32652732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount of Béarn |
E834778
|
entity |
| Predicate | laterTitleOf |
P194351
|
FINISHED |
| Object | kings of Navarre |
—
|
NE NERFINISHED |
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: kings of Navarre | Statement: [Viscount of Béarn, laterTitleOf, kings of Navarre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterTitleOf Context triple: [Viscount of Béarn, laterTitleOf, kings of Navarre]
-
A.
laterTitleHolder
Indicates that one entity is a subsequent holder of a particular title or position previously held by another entity.
-
B.
laterTitleUsage
chosen
Indicates that a title is used or applied to an entity at a later time or in a subsequent context relative to an earlier title usage.
-
C.
earlyTitleOf
Indicates that one entity served as an earlier or preliminary title for another entity.
-
D.
laterTitleOfPatron
Indicates that one title held by a patron chronologically succeeds another title previously held by the same patron.
-
E.
previousTitle
Indicates that one title held or used by an entity directly preceded another title in sequence or time.
- F. None of above.
Provenance (3 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: May 1, 2026, 1:08 a.m.