Triple
T1387420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic Treaty Consultative Meetings |
E29876
|
entity |
| Predicate | firstMeetingHeld |
P12964
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Antarctic Treaty Consultative Meetings, firstMeetingHeld, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMeetingHeld Context triple: [Antarctic Treaty Consultative Meetings, firstMeetingHeld, 1961]
-
A.
firstAssemblyMeeting
Indicates that an entity is the initial or inaugural meeting of a particular assembly or deliberative body.
-
B.
firstMeetingSeason
Indicates the season of the year during which two entities first met.
-
C.
firstMeetingYear
chosen
Indicates the calendar year in which two entities first met or had their initial encounter.
-
D.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
E.
convenedIn
Indicates that an event, meeting, or formal gathering was brought together and held at a specific location.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33b6e108190b6b2bca4ddd97b6c |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.