Triple
T32123601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSRunLoop |
E820441
|
entity |
| Predicate | bridgedWith |
P27599
|
FINISHED |
| Object | CFRunLoopRef |
—
|
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: CFRunLoopRef | Statement: [NSRunLoop, bridgedWith, CFRunLoopRef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgedWith Context triple: [NSRunLoop, bridgedWith, CFRunLoopRef]
-
A.
bridged
chosen
Indicates that one entity has formed a connection or link that spans across or over another entity, effectively joining two previously separated points.
-
B.
bridgedFrom
Indicates that something serves as a connection or transition originating from a specified source or starting point.
-
C.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
D.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
E.
bridgeComponent
Indicates that one entity functions as a structural or functional component of a bridge associated with another entity.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:29 a.m.