Triple
T5673113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A/47/277 |
E125022
|
entity |
| Predicate | hasUNDocumentSymbol |
P53404
|
FINISHED |
| Object | A/47/277 |
—
|
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/47/277 | Statement: [A/47/277, hasUNDocumentSymbol, A/47/277]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUNDocumentSymbol Context triple: [A/47/277, hasUNDocumentSymbol, A/47/277]
-
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.
hasDocumentClass
Indicates that an entity is associated with, or categorized under, a specific class or type of document.
-
D.
hasNotableDocument
Indicates that an entity is associated with a document that is considered significant, noteworthy, or of particular importance.
-
E.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.