Triple
T38587281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockade Prison |
E932372
|
entity |
| Predicate | supportsQuests |
P17730
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Stockade Prison, supportsQuests, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsQuests Context triple: [Stockade Prison, supportsQuests, yes]
-
A.
achievementSupport
Indicates providing assistance, resources, or encouragement that helps an entity achieve goals or reach a desired level of performance.
-
B.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
-
C.
supportsNPCs
Indicates that an entity provides functionality or compatibility for non-player characters (NPCs) within a system or environment.
-
D.
supportGoal
Indicates that one entity actively helps, promotes, or contributes to the achievement of another entity’s goal.
-
E.
supportsMissionType
chosen
Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.