Triple
T33431930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarati |
E856152
|
entity |
| Predicate | earlierThanInUniverse |
P160842
|
FINISHED |
| Object | Tengwar |
—
|
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: Tengwar | Statement: [Sarati, earlierThanInUniverse, Tengwar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierThanInUniverse Context triple: [Sarati, earlierThanInUniverse, Tengwar]
-
A.
precedesInUniverse
chosen
Indicates that one event or entity occurs earlier than another within the timeline or causal order of a given fictional or conceptual universe.
-
B.
notEarlierThan
Indicates that one event, time, or state does not occur before another, i.e., it is simultaneous with or later than the referenced point.
-
C.
locatedInTimeBefore
Indicates that one temporal event or interval occurs entirely before another in time.
-
D.
inUniverseDate
Indicates that an entity is associated with or occurs on a specific date within a fictional or defined universe’s internal timeline.
-
E.
namedAfterInUniverse
Indicates that one entity is, within the fictional or narrative universe, explicitly stated or implied to be named after another entity.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 1, 2026, 1:36 a.m.