Triple
T19447349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impflingen |
E486513
|
entity |
| Predicate | leaderTerm |
P14019
|
FINISHED |
| Object | 2019–2024 |
—
|
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: 2019–2024 | Statement: [Impflingen, leaderTerm, 2019–2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderTerm Context triple: [Impflingen, leaderTerm, 2019–2024]
-
A.
leaderSince
chosen
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
-
B.
targetLeader
Indicates that one entity is the primary leader, focal authority, or main decision-maker targeted or referenced by another entity or action.
-
C.
laterLeader
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
-
D.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
E.
eraLeader
Indicates that a person served as the primary leader or ruler during a specified historical era or period.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338b25d88190bc137a411576c73f |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.