Triple
T29606849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBOR |
E754598
|
entity |
| Predicate | isBinaryAlternativeTo |
P5887
|
FINISHED |
| Object | JSON |
—
|
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: JSON | Statement: [CBOR, isBinaryAlternativeTo, JSON]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBinaryAlternativeTo Context triple: [CBOR, isBinaryAlternativeTo, JSON]
-
A.
isBinary
Indicates that the related entity or value has exactly two possible states, options, or components.
-
B.
isBinaryStandard
Indicates that something conforms to or is expressed in a standard binary (base-2) representation or format.
-
C.
isAlternativeTo
chosen
Indicates that one entity can serve as a substitute or different option in place of another.
-
D.
hasBinary
Indicates that one entity is associated with another entity in a binary (two-component) relationship, typically as one of the two members of a pair.
-
E.
isProprietaryAlternativeTo
Indicates that one entity is a closed-source or commercially restricted substitute for another, typically offering similar functionality under proprietary terms.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66de8aaf48190a2bc6177604a3771 |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:25 p.m.