Triple
T27560904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU-T T.120 |
E695765
|
entity |
| Predicate | conferenceControlDefinedIn |
P163284
|
FINISHED |
| Object | T.124 |
—
|
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: T.124 | Statement: [ITU-T T.120, conferenceControlDefinedIn, T.124]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceControlDefinedIn Context triple: [ITU-T T.120, conferenceControlDefinedIn, T.124]
-
A.
genericConferenceControlDefinedIn
chosen
Indicates that the rules or parameters governing a generic conference are specified or established within a particular defining context or document.
-
B.
conferenceRecognition
Indicates that an entity has received recognition, such as an award, honor, or notable mention, in the context of a specific conference.
-
C.
conferenceType
Indicates the specific category or kind of conference associated with an entity (e.g., workshop, symposium, seminar).
-
D.
governingConference
Indicates that one entity serves as the official organizing or regulatory conference overseeing another entity (such as a team, event, or institution).
-
E.
conference1
Indicates a relationship where an entity is associated with, participates in, or is characterized as a specific conference event or instance.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 1:39 p.m.