Triple
T61537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of Nations |
E1222
|
entity |
| Predicate | lastAssemblyMeeting |
P4554
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [League of Nations, lastAssemblyMeeting, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastAssemblyMeeting Context triple: [League of Nations, lastAssemblyMeeting, 1946]
-
A.
convenes
Indicates bringing people or groups together to formally meet, discuss, or deliberate on a particular matter.
-
B.
legislativeSession
Indicates that an entity is a formal meeting period of a legislative body during which it conducts its official business, such as debating and passing laws.
-
C.
meetingType
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
D.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
E.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a251f74b0881909ad89127b8171277 |
completed | Feb. 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69a24ea242c8819086fe00bf01e6523e |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a251f6786081908eaaed6190695322 |
completed | Feb. 28, 2026, 2:24 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.