Triple
T35604749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John VI of Portugal |
E1028853
|
entity |
| Predicate | titleHeldBeforeAccession |
P159695
|
FINISHED |
| Object | Prince of Brazil |
—
|
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: Prince of Brazil | Statement: [John VI of Portugal, titleHeldBeforeAccession, Prince of Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHeldBeforeAccession Context triple: [John VI of Portugal, titleHeldBeforeAccession, Prince of Brazil]
-
A.
titleHeldBeforeSuccession
chosen
Indicates that an entity held a specific title or position prior to a particular succession event.
-
B.
titleHeldAs
Indicates that an entity holds or possesses a specific title in a particular capacity or role.
-
C.
titleHeldAfter
Indicates that one entity held a particular title or position after another entity, establishing a temporal succession in holding that title.
-
D.
titleHeldAlso
Indicates that an entity holds an additional title concurrently with another title or role.
-
E.
heldTitleFrom
Indicates that an entity possessed or held a particular title starting from a specified point in 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
Created at: May 3, 2026, 4:05 p.m.