Triple
T30569611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Age |
E778088
|
entity |
| Predicate | seriesNumberInLastHundredYearsTrilogy |
P180970
|
FINISHED |
| Object | 3 |
—
|
LITERAL 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: 3 | Statement: [Golden Age, seriesNumberInLastHundredYearsTrilogy, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesNumberInLastHundredYearsTrilogy Context triple: [Golden Age, seriesNumberInLastHundredYearsTrilogy, 3]
-
A.
seriesNumberInTrilogy
Indicates the position or installment number that a work occupies within a specific trilogy.
-
B.
seriesNumberInThrawnTrilogy
Indicates the position or installment number that a work occupies within the Thrawn Trilogy series.
-
C.
seriesNumberInSwordOfHonourTrilogy
Indicates the position or installment number that a work occupies within the "Sword of Honour" trilogy series.
-
D.
hasTrilogy
Indicates that an entity is part of, or associated with, a specific trilogy within a larger set of works or narratives.
-
E.
trilogyDepicts
Indicates that a trilogy portrays, represents, or narratively focuses on a particular subject, event, or set of entities.
- F. None of above. chosen
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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 29, 2026, 8:21 p.m.