Triple
T9498024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolution RC/Res.6 |
E229059
|
entity |
| Predicate | setsEarliestActivationDate |
P83226
|
FINISHED |
| Object | 2017-01-01 |
—
|
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: 2017-01-01 | Statement: [Resolution RC/Res.6, setsEarliestActivationDate, 2017-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsEarliestActivationDate Context triple: [Resolution RC/Res.6, setsEarliestActivationDate, 2017-01-01]
-
A.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
B.
effectivePeriodStart
chosen
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
C.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
-
D.
lessEffectiveAt
Indicates that one entity has a reduced ability or lower level of success in performing, influencing, or achieving a particular action or outcome compared to another.
-
E.
earliestVersionDate
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95ef06b88190b7a840caddea3e38 |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.