Triple
T33111887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ring of Barahir |
E847351
|
entity |
| Predicate | createdInRealm |
P1431
|
FINISHED |
| Object | Nargothrond |
—
|
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: Nargothrond | Statement: [Ring of Barahir, createdInRealm, Nargothrond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdInRealm Context triple: [Ring of Barahir, createdInRealm, Nargothrond]
-
A.
createdIn
chosen
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
-
B.
dateOfCreationAsSeparateRealm
Indicates the point in time when something was first established or recognized as an independent, distinct realm or domain.
-
C.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
-
D.
createdWith
Indicates that something was produced, built, or brought into existence using a particular tool, method, material, or resource.
-
E.
createdUnder
Indicates that something was created during the time period or within the authority, rules, or conditions defined by another entity 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 1, 2026, 1:27 a.m.