Triple
T30530183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spokane Street Bridge |
E776972
|
entity |
| Predicate | hasClearanceType |
P185644
|
FINISHED |
| Object | low-level bridge |
—
|
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: low-level bridge | Statement: [Spokane Street Bridge, hasClearanceType, low-level bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClearanceType Context triple: [Spokane Street Bridge, hasClearanceType, low-level bridge]
-
A.
hasClearance
Indicates that one entity possesses the required authorization level or permission to access or perform actions on another entity or resource.
-
B.
hasClearanceOver
Indicates that one entity possesses authorized access rights or control privileges over another entity or resource.
-
C.
hasClearanceBelow
Indicates that one entity’s clearance level is lower than another entity’s clearance level.
-
D.
hasPlatformClearances
Indicates that an entity possesses the necessary permissions or authorizations to access or operate on a specified platform.
-
E.
clearanceRequired
Indicates that a specific level of authorization or security clearance is needed before the related action can be performed or access can be granted.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 29, 2026, 8:18 p.m.