Triple
T36963714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clockwork Mansion |
E914371
|
entity |
| Predicate | hasPuzzleElement |
P188931
|
FINISHED |
| Object | environmental manipulation |
—
|
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: environmental manipulation | Statement: [Clockwork Mansion, hasPuzzleElement, environmental manipulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPuzzleElement Context triple: [Clockwork Mansion, hasPuzzleElement, environmental manipulation]
-
A.
hasPuzzleDesign
Indicates that one entity is responsible for creating, planning, or defining the structure and content of a puzzle associated with another entity.
-
B.
hasPuzzleSolving
Indicates that an entity possesses the ability or characteristic of solving puzzles or engaging in puzzle-solving activities.
-
C.
hasQuestElement
Indicates that something is a component, step, or requirement that forms part of a larger quest or mission.
-
D.
hasBruteElement
Indicates that an entity possesses or is associated with a raw, force-based, or brute-type elemental property.
-
E.
hasExhibitElement
Indicates that something (such as an exhibit or display) includes or is composed of a particular element or component.
- F. None of above. chosen
Provenance (4 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 3, 2026, 4:14 p.m.