Triple
T10173766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Philip Sousa Bridge |
E235796
|
entity |
| Predicate | isNamedStructureType |
P841
|
FINISHED |
| Object | memorial 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: memorial bridge | Statement: [John Philip Sousa Bridge, isNamedStructureType, memorial bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedStructureType Context triple: [John Philip Sousa Bridge, isNamedStructureType, memorial bridge]
-
A.
hasStructureType
chosen
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
B.
isNamedTree
Indicates that the entity is a tree that has been given a specific name or designation.
-
C.
isNamedUnit
Indicates that an entity is a unit of measurement that has an explicit, conventional name rather than being expressed purely in derived or composite form.
-
D.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
E.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
- 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdeca0dc508190916f2a1bbb288192 |
completed | April 2, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:11 p.m.