Triple
T35823713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ipsach |
E1035572
|
entity |
| Predicate | hasExecutiveTitle |
P36552
|
FINISHED |
| Object | Gemeindepräsident |
—
|
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: Gemeindepräsident | Statement: [Ipsach, hasExecutiveTitle, Gemeindepräsident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExecutiveTitle Context triple: [Ipsach, hasExecutiveTitle, Gemeindepräsident]
-
A.
hasExecutiveHeadTitle
chosen
Indicates the official job title held by the person who serves as the executive head of an organization or entity.
-
B.
hasChiefTitle
Indicates that an entity holds or is associated with a specific chief-level title or designation within an organization or group.
-
C.
hasExecutiveCharacter
Indicates that an entity possesses qualities, authority, or responsibilities characteristic of an executive role.
-
D.
hasRepresentativeTitle
Indicates that an entity holds a formal title or designation that serves as its primary or most commonly used label or name.
-
E.
hasProgramExecutiveOfficerTitle
Indicates that an entity holds the role or designation of a Program Executive Officer.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:06 p.m.