Triple
T20741556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doctor Who: Arc of Infinity |
E510453
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | Ergon |
—
|
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: Ergon | Statement: [Doctor Who: Arc of Infinity, featuresCharacter, Ergon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ergon Context triple: [Doctor Who: Arc of Infinity, featuresCharacter, Ergon]
-
A.
Ergon
chosen
Ergon is a crystalline alien creature from the Doctor Who universe, appearing as a monster in the Fifth Doctor era.
-
B.
Ergolz
Ergolz is a river in the Swiss canton of Basel-Landschaft that flows through the Jura region before joining the Rhine.
-
C.
Korgen
Korgen is a village in Nordland county, Norway, known as the main local hub for services and administration in the municipality of Hemnes.
-
D.
Ericson
Ericson is a Swedish surname borne by various notable individuals, including architect Sigfrid Ericson.
-
E.
Perkins
Perkins is a common English surname borne by numerous notable individuals across politics, arts, sports, and academia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20f9670819082199de21a8d9818 |
completed | April 21, 2026, 12:17 a.m. |
Created at: April 16, 2026, 12:33 p.m.