Triple
T35013332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falinesti |
E1009988
|
entity |
| Predicate | eraKnown |
P84318
|
FINISHED |
| Object | First 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: First Era | Statement: [Falinesti, eraKnown, First Era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraKnown Context triple: [Falinesti, eraKnown, First Era]
-
A.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
B.
eraReference
chosen
Indicates a temporal relationship where something is associated with, situated in, or characterized by a particular historical era or time period.
-
C.
knownInHistoryAs
Indicates that an entity is recognized or referred to by a particular name or title in historical records or accounts.
-
D.
eraOfRomanContact
Indicates the time period during which the entity was in contact or interaction with the Roman world.
-
E.
era
Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.