Triple
T3012853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Trade Organization |
E82263
|
entity |
| Predicate | charterSignedInYear |
P440
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [International Trade Organization, charterSignedInYear, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterSignedInYear Context triple: [International Trade Organization, charterSignedInYear, 1948]
-
A.
charterDate
Indicates the date on which an organization, institution, or entity was formally established or granted its charter.
-
B.
charterAdoptedIn
Indicates that a charter was formally adopted or enacted at a specific time or in a specific place.
-
C.
yearSigned
chosen
Indicates the specific year in which an agreement, contract, or document was formally signed.
-
D.
charterConfirmedBy
Indicates that an official charter has been formally approved or validated by a specified authority or entity.
-
E.
treatySignedYear
Indicates the calendar year in which a specific treaty was formally signed.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a6883c081909b6b74f078e347b7 |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.