Triple
T33076758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU-T X.690 series |
E846384
|
entity |
| Predicate | includesEncodingRule |
P175716
|
FINISHED |
| Object | BER |
E1828174
|
NE 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: BER | Statement: [ITU-T X.690 series, includesEncodingRule, BER]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEncodingRule Context triple: [ITU-T X.690 series, includesEncodingRule, BER]
-
A.
usesEncodingRules
chosen
Indicates that one entity applies or conforms to a specified set of encoding rules when representing or transforming information.
-
B.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
C.
encodingIs
Indicates that one entity serves as the specific encoding or coded representation of another entity.
-
D.
typicalEncoding
Indicates that one entity serves as the standard or most common encoding or representation format used for another entity.
-
E.
representationRules
Indicates the rules or conventions that govern how something is represented, encoded, or depicted in a given context.
- F. None of above.
Provenance (4 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0248062e608190aae1afdae38d2e5a |
completed | May 11, 2026, 9:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34f013dd14819085388cb3fd375e57 |
completed | June 19, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a02465a0d38819084c3a6813fb943fc |
completed | May 11, 2026, 9:12 p.m. |
Created at: May 1, 2026, 1:25 a.m.