Triple
T35511299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northpoint |
E1026290
|
entity |
| Predicate | factionEra |
P18945
|
FINISHED |
| Object | Daggerfall Covenant (Second Era) |
—
|
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: Daggerfall Covenant (Second Era) | Statement: [Northpoint, factionEra, Daggerfall Covenant (Second Era)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionEra Context triple: [Northpoint, factionEra, Daggerfall Covenant (Second Era)]
-
A.
primaryAllegianceEra
Indicates the historical period or era during which an entity’s main allegiance or loyalty was primarily held.
-
B.
historicalFaction
Indicates that an entity was a member of, associated with, or part of a particular faction or side in a historical context or conflict.
-
C.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
D.
fictionalEra
chosen
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
E.
historical era
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:04 p.m.