Triple
T9625731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erathem |
E232458
|
entity |
| Predicate | timeEquivalent |
P12099
|
FINISHED |
| Object | 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: era | Statement: [Erathem, timeEquivalent, era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeEquivalent Context triple: [Erathem, timeEquivalent, era]
-
A.
timeEquivalentOf
chosen
Indicates that two temporal entities represent the same point in time or duration, possibly expressed in different formats or units.
-
B.
timeDescribedAs
Indicates that a specific time or temporal interval is characterized, labeled, or expressed using a particular description or representation.
-
C.
timeInterpretation
Indicates how a given temporal expression or event should be understood or interpreted in terms of time (e.g., its reference point, scope, or temporal role).
-
D.
timeDifferenceWith
Indicates a relationship where the temporal difference or interval between two time points, events, or entities is specified or measured.
-
E.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afb67c88190aa170716f0033752 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.