Triple
T37662931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caves & Cliffs: Part I |
E937755
|
entity |
| Predicate | addsMob |
P40431
|
FINISHED |
| Object | goat |
—
|
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: goat | Statement: [Caves & Cliffs: Part I, addsMob, goat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsMob Context triple: [Caves & Cliffs: Part I, addsMob, goat]
-
A.
addsVillain
Indicates that one entity introduces or includes another entity in the role of a villain within a given context or storyline.
-
B.
hasMob
chosen
Indicates that an entity possesses, controls, or is associated with a particular mob or group of mobile agents.
-
C.
associatedMob
Indicates a relationship where one entity is linked or connected to a particular mob (mobile entity), typically as its counterpart, partner, or related unit.
-
D.
addsRaid
Indicates that an entity initiates or includes a raid event or operation involving another entity.
-
E.
addsNPCType
Indicates that one entity introduces or registers a specific type of non-player character (NPC) into a system, context, or environment.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.