Triple
T37873344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossroads |
E944657
|
entity |
| Predicate | hasRepairNPC |
P170697
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Crossroads, hasRepairNPC, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepairNPC Context triple: [Crossroads, hasRepairNPC, true]
-
A.
isRepairable
Indicates that an entity can be restored to proper working condition through repair.
-
B.
hasNPC
chosen
Indicates that an entity includes, is associated with, or contains a non-player character (NPC) within its context or structure.
-
C.
repairedIn
Indicates that an item or object underwent repair within a specified location or during a particular time period.
-
D.
hasRestorationWorkBy
Indicates that an entity has undergone restoration work carried out by a specified agent or party.
-
E.
requiresNPC
Indicates that one entity depends on the presence, involvement, or assistance of a non-player character (NPC) in order to occur, be valid, or be completed.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.