Triple
T28374870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorcerer’s Workshop |
E718728
|
entity |
| Predicate | hasNoHeightRequirement |
P199169
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sorcerer’s Workshop, hasNoHeightRequirement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoHeightRequirement Context triple: [Sorcerer’s Workshop, hasNoHeightRequirement, true]
-
A.
heightRestriction
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
B.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
C.
standingRequired
Indicates that a certain status, condition, or eligibility (“standing”) is required for an entity to participate in or perform a particular action or relationship.
-
D.
qualificationHeight
Indicates that an entity meets or is associated with a specified minimum or required height threshold for a particular purpose or qualification.
-
E.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff246e0d4481908bcec718e1d4025b |
completed | May 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69ff23cb70ac81909b776ace4597ae9c |
completed | May 9, 2026, 12:08 p.m. |
| PDg | Predicate description generation | batch_69ff246d53cc81909d5528224149b04b |
completed | May 9, 2026, 12:11 p.m. |
Created at: April 28, 2026, 1:02 a.m.