Triple
T37698633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO Annexes |
E938992
|
entity |
| Predicate | firstAnnexAdoptedIn |
P204346
|
FINISHED |
| Object | 1940s |
—
|
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: 1940s | Statement: [ICAO Annexes, firstAnnexAdoptedIn, 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAnnexAdoptedIn Context triple: [ICAO Annexes, firstAnnexAdoptedIn, 1940s]
-
A.
annexationDate
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
-
B.
annexedInYear
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
-
C.
annexationInstrument
Indicates the legal or formal instrument (such as a treaty, decree, or law) by which one entity annexes or incorporates another.
-
D.
annexedDuring
Indicates that one entity was formally incorporated into and brought under the control of another entity during a specified time period.
-
E.
northernPartAnnexedBy
Indicates that the northern portion of an entity has been taken over and incorporated into another entity.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.