Triple
T37512623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldstone |
E932552
|
entity |
| Predicate | fragmentsAppearIn |
P795
|
FINISHED |
| Object | Diablo Immortal |
—
|
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: Diablo Immortal | Statement: [Worldstone, fragmentsAppearIn, Diablo Immortal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fragmentsAppearIn Context triple: [Worldstone, fragmentsAppearIn, Diablo Immortal]
-
A.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
B.
appearsIn
chosen
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
C.
reappearsIn
Indicates that an entity that previously appeared becomes present or visible again in the same or another context.
-
D.
appearsFrom
Indicates that one entity becomes visible or emerges originating from another entity or location.
-
E.
appearsInContextWith
Indicates that two entities are observed or used together within the same situational, textual, or usage 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.