Triple
T4647137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Minister with portfolio |
E102198
|
entity |
| Predicate | eligiblePerson |
P84
|
FINISHED |
| Object | German citizen |
—
|
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: German citizen | Statement: [Federal Minister with portfolio, eligiblePerson, German citizen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligiblePerson Context triple: [Federal Minister with portfolio, eligiblePerson, German citizen]
-
A.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
B.
eligibleOn
Indicates the date or condition from which something qualifies to begin or be considered valid or applicable.
-
C.
eligibility
chosen
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
D.
positionEligible
Indicates that an entity is qualified or permitted to hold or be assigned to a particular position or role.
-
E.
eligibleBorrower
Indicates that an entity meets the required conditions to be allowed to borrow (e.g., money, items, or resources) under a given set of rules or policies.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.