Triple
T20564682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samoa Agreement |
E504935
|
entity |
| Predicate | startOfValidity |
P83226
|
FINISHED |
| Object | 2024 |
—
|
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: 2024 | Statement: [Samoa Agreement, startOfValidity, 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfValidity Context triple: [Samoa Agreement, startOfValidity, 2024]
-
A.
effectivePeriodStart
chosen
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
B.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
C.
startDateConstraint
Indicates a restriction or condition placed on when something is allowed to start, typically specifying valid or required start dates.
-
D.
startDateRule
Indicates the rule or condition that determines when something is allowed or required to start.
-
E.
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.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a15c988190ba93823df119ca4d |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.