Triple
T35138051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abecean Sea |
E1014625
|
entity |
| Predicate | inLoreEra |
P18945
|
FINISHED |
| Object | First Era |
—
|
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: First Era | Statement: [Abecean Sea, inLoreEra, First Era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inLoreEra Context triple: [Abecean Sea, inLoreEra, First Era]
-
A.
fictionalEra
chosen
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
B.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
C.
yearInLore
Indicates the specific in-universe year, according to a fictional or narrative timeline, in which an event or state occurs.
-
D.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
E.
introductionEra
Indicates the historical period or era during which something was first introduced or came into use.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.