Triple
T10172111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beştepe |
E235355
|
entity |
| Predicate | hasTypeOfGovernmentalFunction |
P3902
|
FINISHED |
| Object | executive |
—
|
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: executive | Statement: [Beştepe, hasTypeOfGovernmentalFunction, executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfGovernmentalFunction Context triple: [Beştepe, hasTypeOfGovernmentalFunction, executive]
-
A.
basedInGovernmentType
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
-
B.
governmentalFunction
chosen
Indicates that an entity performs, embodies, or is responsible for an official role, duty, or activity of a government.
-
C.
targetGovernmentType
Indicates the form or system of governance that an entity is directed toward, associated with, or intended to influence.
-
D.
typeOfGovernmentInstitution
Indicates that one entity is a government institution of the type or category specified by the other entity.
-
E.
governmentalUnitType
Indicates the specific category or classification of a governmental unit (such as federal, state, municipal, or other administrative level) that an entity belongs to.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9e4e0c819097dceb7bf7757948 |
completed | April 2, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.