Triple
T33057075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X.680 series |
E845870
|
entity |
| Predicate | encodingRulesSpecifiedIn |
P150144
|
FINISHED |
| Object | X.690 series |
—
|
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: X.690 series | Statement: [X.680 series, encodingRulesSpecifiedIn, X.690 series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encodingRulesSpecifiedIn Context triple: [X.680 series, encodingRulesSpecifiedIn, X.690 series]
-
A.
representationRules
chosen
Indicates the rules or conventions that govern how something is represented, encoded, or depicted in a given context.
-
B.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
C.
extendsSpecificationDefinedIn
Indicates that one specification builds upon, elaborates, or broadens the scope of another previously defined specification.
-
D.
specifiedFor
Indicates that something is designated or intended to be used for a particular entity, purpose, or context.
-
E.
encodingScope
Indicates the range or extent of content or information that is covered, represented, or captured by a particular encoding.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.