Triple
T11559857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice President of the Bundestag |
E274112
|
entity |
| Predicate | canStandInFor |
P6726
|
FINISHED |
| Object | President of the Bundestag |
—
|
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: President of the Bundestag | Statement: [Vice President of the Bundestag, canStandInFor, President of the Bundestag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canStandInFor Context triple: [Vice President of the Bundestag, canStandInFor, President of the Bundestag]
-
A.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
B.
canRepresent
chosen
Indicates that one entity is capable of serving as a valid stand-in, proxy, or expression for another entity in a given context.
-
C.
canServeOn
Indicates that one entity is eligible or permitted to serve on another entity, such as a group, body, or committee.
-
D.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
E.
isStandOf
Indicates that one entity serves as the Stand (a supernatural or personified power) belonging to or associated with another entity.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a899d4481909a3bce3147763b51 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.