Triple
T61978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Secretary General |
E1231
|
entity |
| Predicate | officeHolderType |
P2718
|
FINISHED |
| Object | civilian |
—
|
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: civilian | Statement: [NATO Secretary General, officeHolderType, civilian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHolderType Context triple: [NATO Secretary General, officeHolderType, civilian]
-
A.
officeHolderOf
Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
-
B.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
C.
headOfGovernmentBody
Indicates that one entity serves as the chief executive or leading official in charge of governing another entity, typically a political or administrative body.
-
D.
officeHoldersMustBe
chosen
Indicates that individuals who hold a particular office are required to possess a specified status, qualification, or characteristic.
-
E.
hasChiefExecutiveRole
Indicates that an entity holds the highest executive leadership position and overall managerial authority within an organization.
- 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_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. |
Created at: Feb. 28, 2026, 2:02 a.m.