Triple
T10881522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosebrough Tiger Passage |
E256930
|
entity |
| Predicate | featuresBarrierType |
P53911
|
FINISHED |
| Object | mesh tunnels above visitor pathways |
—
|
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: mesh tunnels above visitor pathways | Statement: [Rosebrough Tiger Passage, featuresBarrierType, mesh tunnels above visitor pathways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBarrierType Context triple: [Rosebrough Tiger Passage, featuresBarrierType, mesh tunnels above visitor pathways]
-
A.
typicalBarrierType
chosen
Indicates the usual or characteristic type of barrier associated with or used in a given context or situation.
-
B.
isBarrierTo
Indicates that one entity obstructs, prevents, or significantly hinders another entity from occurring, progressing, or being accessed.
-
C.
gateType
Indicates the specific kind or classification of a gate associated with an entity.
-
D.
doorType
Indicates the specific kind or category of door associated with an entity.
-
E.
hasGuardBars
Indicates that one entity is equipped with or protected by guard bars installed on or around it.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751da559c819094c3680a9f734ee7 |
completed | April 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.