Triple
T28284890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nescio Bridge |
E713254
|
entity |
| Predicate | hasRampApproaches |
P119068
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nescio Bridge, hasRampApproaches, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRampApproaches Context triple: [Nescio Bridge, hasRampApproaches, yes]
-
A.
containsRamps
chosen
Indicates that one entity includes or is equipped with one or more ramps as part of its structure or features.
-
B.
hasRampSpace
Indicates that a location or structure includes designated space for a ramp, allowing sloped access between different levels.
-
C.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
D.
hasVehicleLoadingRamps
Indicates that something is equipped with ramps specifically intended for loading or unloading vehicles.
-
E.
hasEntranceElevation
Indicates the elevation at which an entity’s entrance is located, typically measured relative to a reference level such as sea level or ground level.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 11:25 p.m.