Triple
T27745444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John, Prince of Asturias |
E701968
|
entity |
| Predicate | traditionalTitleHeld |
P39110
|
FINISHED |
| Object | Prince of Asturias |
—
|
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 Asturias | Statement: [John, Prince of Asturias, traditionalTitleHeld, Prince of Asturias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalTitleHeld Context triple: [John, Prince of Asturias, traditionalTitleHeld, Prince of Asturias]
-
A.
traditionalTitleHolder
chosen
Indicates that one entity holds a customary or historically established title or rank in relation to another entity.
-
B.
titleHeldAs
Indicates that an entity holds or possesses a specific title in a particular capacity or role.
-
C.
titleHeldTo
Indicates that one entity holds or possesses a specific title in relation to another entity or context.
-
D.
titleHeldThrough
Indicates that an entity holds or possesses a title by means of, or via the intermediary of, another entity or mechanism.
-
E.
traditionalTitleGivenBy
Indicates that one entity has conferred or assigned a traditional or customary title to another entity.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 27, 2026, 4:15 p.m.