Triple
T30633203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elven-smiths of Eregion |
E779764
|
entity |
| Predicate | activeInAge |
P178824
|
FINISHED |
| Object | Second Age |
—
|
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: Second Age | Statement: [Elven-smiths of Eregion, activeInAge, Second Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInAge Context triple: [Elven-smiths of Eregion, activeInAge, Second Age]
-
A.
activeInYears
Indicates that an entity was active or operational during the specified years or year range.
-
B.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
-
C.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
D.
activeInYear
Indicates that an entity was active, functioning, or operational during a specified year.
-
E.
activeYearsWith
Indicates the span of time during which an entity was actively engaged in a particular role, activity, or association with another entity.
- F. None of above. chosen
Provenance (4 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 29, 2026, 8:28 p.m.