Triple
T1429993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erwin König |
E30420
|
entity |
| Predicate | existenceStatus |
P127
|
FINISHED |
| Object | likely fictional |
—
|
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: likely fictional | Statement: [Erwin König, existenceStatus, likely fictional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existenceStatus Context triple: [Erwin König, existenceStatus, likely fictional]
-
A.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
B.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
C.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
E.
coordinateStatus
Indicates that one entity’s status is aligned, synchronized, or made consistent with another entity’s status or with a shared reference state.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.