Triple
T20573501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hitman (selected titles) |
E505156
|
entity |
| Predicate | missionStructure |
P42111
|
FINISHED |
| Object | large open levels |
—
|
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: large open levels | Statement: [Hitman (selected titles), missionStructure, large open levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionStructure Context triple: [Hitman (selected titles), missionStructure, large open levels]
-
A.
segmentMission
Indicates that a specific mission is associated with, assigned to, or carried out within a particular segment or phase.
-
B.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
C.
missionConfiguration
Indicates the specific setup, parameters, and conditions under which a mission is planned or executed.
-
D.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
-
E.
missionDesign
chosen
Indicates the relationship in which an entity plans, structures, and specifies the objectives, constraints, and procedures for carrying out a mission.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a9087af88190a4610ecb29f637ca |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.