Triple
T1303730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCCh |
E27825
|
entity |
| Predicate | boardAppointmentBy |
P26802
|
FINISHED |
| Object | President of Chile |
—
|
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: President of Chile | Statement: [BCCh, boardAppointmentBy, President of Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardAppointmentBy Context triple: [BCCh, boardAppointmentBy, President of Chile]
-
A.
appointmentBy
Indicates that one entity is appointed or designated to a role, position, or task by another entity.
-
B.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
C.
appointedAs
Indicates that one entity is formally assigned or designated to hold a specific role, position, or title in relation to another entity.
-
D.
boardingGroups
Indicates that certain entities are assigned to or associated with specific boarding groups for an ordered boarding process.
-
E.
appointmentOnAdviceOf
Indicates that an appointment or selection of someone to a position is made based on the recommendation, counsel, or formal advice of another person or authority.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c116d7d881908ee631258f80980e |
completed | March 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:51 p.m.