Triple
T38575477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations General Assembly Resolution 106 (S-1) |
E929388
|
entity |
| Predicate | hasSessionCode |
P203010
|
FINISHED |
| Object | S-1 |
—
|
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: S-1 | Statement: [United Nations General Assembly Resolution 106 (S-1), hasSessionCode, S-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSessionCode Context triple: [United Nations General Assembly Resolution 106 (S-1), hasSessionCode, S-1]
-
A.
hasIneCode
Indicates that an entity is associated with a specific INE (national statistics or education) code that identifies it in an official registry.
-
B.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
C.
hasConferenceCode
Indicates that a conference is associated with a specific identifying code.
-
D.
hasSignCode
Indicates that an entity is associated with a specific sign identifier or code used to represent it.
-
E.
hasCodeA
Indicates that an entity is associated with or assigned a specific code labeled as type A.
- F. None of above. chosen
Provenance (4 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00d9717a9881908194163d719f14d6 |
completed | May 10, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a00d91db2ec81909ebacfc9f0d11dd8 |
completed | May 10, 2026, 7:14 p.m. |
| PDg | Predicate description generation | batch_6a00d970a11081908f24876a0696d827 |
completed | May 10, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.