Triple
T32569195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herman IV, Duke of Swabia |
E832461
|
entity |
| Predicate | hasNoKnownIssue |
P82927
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Herman IV, Duke of Swabia, hasNoKnownIssue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoKnownIssue Context triple: [Herman IV, Duke of Swabia, hasNoKnownIssue, true]
-
A.
hasNoIssue
chosen
Indicates that there are no problems, defects, or conflicts associated with the referenced entity or situation.
-
B.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
-
C.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
D.
hasIssueRecognizedBy
Indicates that an issue or problem is acknowledged, identified, or formally recognized by a particular entity.
-
E.
knownIssue
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01378bf05c8190af9f5e06a2810c7d |
completed | May 11, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_6a0137277c6c8190bcec341f2a0757c4 |
completed | May 11, 2026, 1:55 a.m. |
Created at: May 1, 2026, 1:03 a.m.