Triple
T11659904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep Dark |
E277094
|
entity |
| Predicate | playerObjective |
P67602
|
FINISHED |
| Object | careful looting of Ancient Cities |
—
|
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: careful looting of Ancient Cities | Statement: [Deep Dark, playerObjective, careful looting of Ancient Cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerObjective Context triple: [Deep Dark, playerObjective, careful looting of Ancient Cities]
-
A.
actorObjective
Indicates that an actor has a specific goal, purpose, or intended outcome in relation to another entity or situation.
-
B.
gameObjective
chosen
Indicates the primary goal or intended outcome that participants aim to achieve within a game.
-
C.
opponentObjective
Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
-
D.
secretObjective
Indicates that an entity has a hidden or undisclosed goal or target that is not known to others.
-
E.
notableObjective
Indicates that an entity has a significant, distinguished, or widely recognized goal, purpose, or target associated with it.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.