Triple
T38479917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roebling family |
E915642
|
entity |
| Predicate | knownForStructure |
P21878
|
FINISHED |
| Object | Brooklyn Bridge |
—
|
NE NERFINISHED |
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: Brooklyn Bridge | Statement: [Roebling family, knownForStructure, Brooklyn Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForStructure Context triple: [Roebling family, knownForStructure, Brooklyn Bridge]
-
A.
bestKnownStructure
chosen
Indicates that the related entity is the most prominent or widely recognized structure associated with the subject.
-
B.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
C.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
D.
significantStructureWithin
Indicates that one structure is an important or notable part located inside another structure.
-
E.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.