Triple
T8114099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifth Committee |
E189427
|
entity |
| Predicate | usesDocumentationSymbol |
P53404
|
FINISHED |
| Object | A/C.5 |
—
|
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: A/C.5 | Statement: [Fifth Committee, usesDocumentationSymbol, A/C.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDocumentationSymbol Context triple: [Fifth Committee, usesDocumentationSymbol, A/C.5]
-
A.
hasDocumentSymbol
chosen
Indicates that an entity is associated with a particular document symbol or identifier used to reference that document.
-
B.
hasDocumentationAt
Indicates that something is documented or described in a specific document, file, or location.
-
C.
symbolicallyUses
Indicates that one entity employs another as a symbol or representation to convey meaning, ideas, or associations rather than for its literal or practical function.
-
D.
hasLimitedDocumentation
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
-
E.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
Created at: March 30, 2026, 5:32 p.m.