Triple
T4154625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU Member States |
E91386
|
entity |
| Predicate | sign |
P150
|
FINISHED |
| Object | Final Acts of ITU conferences |
—
|
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: Final Acts of ITU conferences | Statement: [ITU Member States, sign, Final Acts of ITU conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sign Context triple: [ITU Member States, sign, Final Acts of ITU conferences]
-
A.
signature
chosen
Indicates that one entity has provided an official or personal signed endorsement, authorization, or acknowledgment on or for another entity.
-
B.
signInterpretation
Indicates that one entity provides or assigns a particular meaning, explanation, or reading to a given sign, symbol, or signal.
-
C.
signText
Indicates that a sign bears or displays a particular textual content.
-
D.
signedAs
Indicates that an entity has signed or endorsed something using a particular name, role, or identity.
-
E.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.