Triple
T3514367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dwarfie Stane |
E74270
|
entity |
| Predicate | hasDoorway |
P6140
|
FINISHED |
| Object | small rectangular entrance |
—
|
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: small rectangular entrance | Statement: [Dwarfie Stane, hasDoorway, small rectangular entrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoorway Context triple: [Dwarfie Stane, hasDoorway, small rectangular entrance]
-
A.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
-
B.
hasStageDoor
Indicates that a venue or building possesses a dedicated stage door used for performers and staff to access backstage areas.
-
C.
hasEntrance
chosen
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
D.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
E.
hasEndDoors
Indicates that an object or structure is equipped with doors located at one or more of its ends.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc2efa4c8190ac1ca221f3f0eba4 |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.