Triple
T16343019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/RES/1244(1999) |
E396854
|
entity |
| Predicate | hasFullTextURL |
P6969
|
FINISHED |
| Object | https://undocs.org/S/RES/1244(1999) |
—
|
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: https://undocs.org/S/RES/1244(1999) | Statement: [S/RES/1244(1999), hasFullTextURL, https://undocs.org/S/RES/1244(1999)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFullTextURL Context triple: [S/RES/1244(1999), hasFullTextURL, https://undocs.org/S/RES/1244(1999)]
-
A.
hasFullTextAvailableAt
chosen
Indicates that the complete text of a resource is accessible at a specified location or via a given link.
-
B.
hasText
Indicates that an entity is associated with or contains a specific piece of textual content.
-
C.
hasReferenceURL
Indicates that an entity is associated with a specific web address that serves as a reference or source of additional information about it.
-
D.
hasFullForm
Indicates that one entity is the complete, expanded, or unabbreviated form of another entity.
-
E.
hasPrimaryURL
Indicates that an entity is associated with its main or canonical web address (URL).
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da0b88d081908a99cafa8e0ae5db |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.