Triple
T17569293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BidirectionalCollection |
E427892
|
entity |
| Predicate | superProtocol |
P81486
|
FINISHED |
| Object | Collection |
—
|
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: Collection | Statement: [BidirectionalCollection, superProtocol, Collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superProtocol Context triple: [BidirectionalCollection, superProtocol, Collection]
-
A.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
B.
parentProtocol
chosen
Indicates that one protocol serves as the direct ancestor or higher-level specification from which another protocol is derived or extended.
-
C.
primaryProtocol
Indicates that one protocol is designated as the main or default protocol used in a given context or interaction.
-
D.
targetProtocol
Indicates the communication protocol that an action, message, or connection is intended to use or be directed toward.
-
E.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
- 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_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. |
Created at: April 10, 2026, 5:50 a.m.