Triple
T38587616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deeprun Tram entrance |
E932379
|
entity |
| Predicate | designedByRace |
P173326
|
FINISHED |
| Object | gnomes (lore) |
—
|
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: gnomes (lore) | Statement: [Deeprun Tram entrance, designedByRace, gnomes (lore)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedByRace Context triple: [Deeprun Tram entrance, designedByRace, gnomes (lore)]
-
A.
forgedByRace
chosen
Indicates that something was created or shaped through the actions or influence of a particular race or species.
-
B.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
C.
hasRace
Indicates that an entity possesses or is characterized by a particular race or racial classification.
-
D.
designedByFamilyOf
Indicates that something was created, planned, or conceived by one or more members of a particular family or familial group.
-
E.
hasFeatureRace
Indicates that an entity includes, offers, or is associated with a specific race-related feature or race event.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:32 p.m.