Triple
T17569068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bool |
E427887
|
entity |
| Predicate | bridgedFrom |
P128030
|
FINISHED |
| Object | ObjC BOOL via Foundation |
—
|
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: ObjC BOOL via Foundation | Statement: [Bool, bridgedFrom, ObjC BOOL via Foundation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgedFrom Context triple: [Bool, bridgedFrom, ObjC BOOL via Foundation]
-
A.
bridged
Indicates that one entity has formed a connection or link that spans across or over another entity, effectively joining two previously separated points.
-
B.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
C.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
D.
bridgeReplaced
Indicates that one bridge has been substituted or exchanged for another, typically as a result of construction, repair, or upgrade.
-
E.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592f29d08190bc3de905d35af849 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.