Triple
T386996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Johns Bridge |
E8799
|
entity |
| Predicate | hasApproachType |
P10782
|
FINISHED |
| Object | steel deck truss |
—
|
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: steel deck truss | Statement: [St. Johns Bridge, hasApproachType, steel deck truss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproachType Context triple: [St. Johns Bridge, hasApproachType, steel deck truss]
-
A.
includesApproach
Indicates that one entity incorporates, utilizes, or is characterized by a particular method, strategy, or approach in relation to another entity or context.
-
B.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
C.
hasInstrumentApproach
Indicates that an approach procedure to a location or runway is conducted using specified navigation instruments or instrument-based methods.
-
D.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
E.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5828d881909e8810061c02480c |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e967d84c8190a6b647f78d95d4e4 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea2dc3088190a2aeb4496aff3582 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.