Triple
T33216987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elves of Lothlórien |
E850314
|
entity |
| Predicate | firstAgeOrigin |
P192650
|
FINISHED |
| Object | Sindarin and Silvan ancestry |
—
|
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: Sindarin and Silvan ancestry | Statement: [Elves of Lothlórien, firstAgeOrigin, Sindarin and Silvan ancestry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAgeOrigin Context triple: [Elves of Lothlórien, firstAgeOrigin, Sindarin and Silvan ancestry]
-
A.
hasOriginAge
chosen
Indicates that an entity is associated with the age or time period when it first originated or came into existence.
-
B.
firstGenerationOrigin
Indicates that an entity originates from the first generation within a defined lineage, cycle, or sequence.
-
C.
firstStageOrigin
Indicates that one entity is the original source or starting point of the first stage of another entity or process.
-
D.
firstGenerationStart
Indicates the point in time or event at which the first generation in a sequence, lineage, or series begins.
-
E.
oldestAge
Indicates that the associated value represents the greatest (maximum) age within a given group, set, or context.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:30 a.m.