Triple
T19985733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Room of Requirement |
E493924
|
entity |
| Predicate | canBeEnteredFrom |
P1974
|
FINISHED |
| Object | opposite the tapestry of Barnabas the Barmy |
—
|
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: opposite the tapestry of Barnabas the Barmy | Statement: [Room of Requirement, canBeEnteredFrom, opposite the tapestry of Barnabas the Barmy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeEnteredFrom Context triple: [Room of Requirement, canBeEnteredFrom, opposite the tapestry of Barnabas the Barmy]
-
A.
hasEntranceOn
chosen
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
B.
entersFrom
Indicates that one entity moves into or arrives at a place, state, or context by coming from another specified source or location.
-
C.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
D.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
-
E.
hasNumberOfEntrances
Indicates the relationship that specifies how many entrances an entity possesses.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d162b008190a18d325796d75d77 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:29 p.m.