Triple
T2036495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clara E. Coffey |
E44641
|
entity |
| Predicate | hasUncertainRoleIn |
P28456
|
FINISHED |
| Object | design of the Bear Mountain 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: design of the Bear Mountain Bridge | Statement: [Clara E. Coffey, hasUncertainRoleIn, design of the Bear Mountain Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUncertainRoleIn Context triple: [Clara E. Coffey, hasUncertainRoleIn, design of the Bear Mountain Bridge]
-
A.
possibleRole
chosen
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
B.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
C.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
D.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
E.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9363b608190b42aa6d3f3fd78c4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.