Triple
T7665309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge |
E173609
|
entity |
| Predicate | abstractionHas |
P59095
|
FINISHED |
| Object | Implementor reference |
—
|
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: Implementor reference | Statement: [Bridge, abstractionHas, Implementor reference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abstractionHas Context triple: [Bridge, abstractionHas, Implementor reference]
-
A.
providesAbstraction
chosen
Indicates that one entity offers a higher-level, simplified interface or conceptual layer that hides the underlying complexity of another entity.
-
B.
includesAbstract
Indicates that one entity contains or incorporates the abstract or summary section of another entity.
-
C.
isAbstractVersionOf
Indicates that one entity represents a conceptual, generalized, or non-concrete version of another, more specific or concrete entity.
-
D.
hasRealizationAs
Indicates that something abstract, such as a plan, design, or concept, is concretely implemented or manifested as a particular realized form.
-
E.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
- 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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.