Triple
T27209263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tintin in the Congo |
E683953
|
entity |
| Predicate | workChronologyNumberInSeries |
P5172
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Tintin in the Congo, workChronologyNumberInSeries, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workChronologyNumberInSeries Context triple: [Tintin in the Congo, workChronologyNumberInSeries, 2]
-
A.
workChronologyPosition
chosen
Indicates the relative ordering or position of a work within a sequence of works, such as in a career, series, or catalog.
-
B.
sequenceInWork
Indicates that one work appears as a sequential part or installment within a larger overarching work.
-
C.
seriesNumberOfWorks
Indicates that an entity is assigned a specific position or sequence number within a series of related works.
-
D.
workNumbering
Indicates that a specific numbering or cataloging identifier is assigned to a work within a larger collection or system.
-
E.
chronologicalOrderInSeries
Indicates that one entity appears earlier or later than another within an ordered sequence or series.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625e8342c8190a809bfb169967a89 |
completed | May 2, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:39 a.m.