Triple
T15924984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hufeisenplan |
E386183
|
entity |
| Predicate | allegedDocumentStatus |
P16813
|
FINISHED |
| Object | never independently verified |
—
|
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: never independently verified | Statement: [Hufeisenplan, allegedDocumentStatus, never independently verified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedDocumentStatus Context triple: [Hufeisenplan, allegedDocumentStatus, never independently verified]
-
A.
allegedStatus
chosen
Indicates that a particular status or condition is claimed or asserted about an entity, but has not been confirmed as true.
-
B.
statusOfClaim
Indicates the current state or condition of a specific claim within a process or system.
-
C.
complainantStatus
Indicates the role or standing of the person or party making a complaint in relation to the case or issue.
-
D.
disputeStatus
Indicates the current state or condition of a disagreement or conflict between parties.
-
E.
respondentStatus
Indicates the current role, condition, or state of a respondent in relation to a survey, inquiry, or legal/administrative process.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.