Triple
T24489744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greywell Tunnel |
E617608
|
entity |
| Predicate | entranceVisibility |
P156506
|
FINISHED |
| Object | eastern portal visible |
—
|
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: eastern portal visible | Statement: [Greywell Tunnel, entranceVisibility, eastern portal visible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceVisibility Context triple: [Greywell Tunnel, entranceVisibility, eastern portal visible]
-
A.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
B.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
C.
entranceHeight
Indicates the vertical measurement of how tall an entrance is.
-
D.
entranceSize
Indicates the size or dimensions of an entrance relative to a referenced object or structure.
-
E.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a9d795288190916368e3cec1f666 |
completed | April 30, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:22 a.m.