Triple
T38447349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naugrim |
E906674
|
entity |
| Predicate | firstAgeUsage |
P204657
|
FINISHED |
| Object | First Age of Middle-earth |
E261178
|
NE 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: First Age of Middle-earth | Statement: [Naugrim, firstAgeUsage, First Age of Middle-earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAgeUsage Context triple: [Naugrim, firstAgeUsage, First Age of Middle-earth]
-
A.
firstUsedAs
Indicates that one entity was the earliest or original thing in which another entity was used or applied.
-
B.
firstYearOfUse
Indicates the year in which something was first put into use or began being used.
-
C.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
D.
firstUsedAt
Indicates the time or place at which something was initially used or put into operation.
-
E.
earlyUse
Indicates that an entity is used or adopted at an unusually early time or stage relative to a typical or expected point of use.
- F. None of above. chosen
Provenance (5 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41c2a16fa8819080f1dcaa2fd0a8d0 |
completed | June 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:31 p.m.