Triple
T31951463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quilín |
E815789
|
entity |
| Predicate | meetingTypeHeld |
P3082
|
FINISHED |
| Object | diplomatic parliament |
—
|
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: diplomatic parliament | Statement: [Quilín, meetingTypeHeld, diplomatic parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingTypeHeld Context triple: [Quilín, meetingTypeHeld, diplomatic parliament]
-
A.
meetingType
chosen
Indicates the specific category or format of a meeting that characterizes how it is organized or conducted.
-
B.
meetingsWere
Indicates that one or more meetings occurred or were held between the referenced entities.
-
C.
hasMeeting
Indicates that one entity is scheduled to participate in or hold a meeting with another entity or at a specific time or place.
-
D.
meetingPeriod
Indicates the time span or duration during which a meeting takes place.
-
E.
meetingState
Indicates the current status or phase of a meeting within its overall lifecycle (e.g., scheduled, in progress, or completed).
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2a9fadc8190a3b5a5afdbdc82aa |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:07 a.m.