Triple
T37512395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inarius |
E932547
|
entity |
| Predicate | goalInDiabloIV |
P100703
|
FINISHED |
| Object | to confront Lilith |
—
|
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: to confront Lilith | Statement: [Inarius, goalInDiabloIV, to confront Lilith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalInDiabloIV Context triple: [Inarius, goalInDiabloIV, to confront Lilith]
-
A.
goalIn
chosen
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
B.
goalInDayOfTheTentacle
Indicates that something serves as a goal or objective within the context of the game "Day of the Tentacle."
-
C.
gameObjective
Indicates the primary goal or intended outcome that participants aim to achieve within a game.
-
D.
hasRitualGoal
Indicates that an action, practice, or ritual is performed with the specific purpose of achieving a particular ritualistic outcome or objective.
-
E.
goalsFor
Indicates the number of goals scored by one participant or team in favor of a particular side or match 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_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.