Triple
T9405622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustav von Aschenbach |
E226578
|
entity |
| Predicate | physicalArc |
P88996
|
FINISHED |
| Object | decline |
—
|
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: decline | Statement: [Gustav von Aschenbach, physicalArc, decline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalArc Context triple: [Gustav von Aschenbach, physicalArc, decline]
-
A.
physicalRequirement
Indicates that one entity specifies a necessary physical condition, capability, or resource that must be met or possessed for another entity, action, or process to occur or be valid.
-
B.
physicalBasis
Indicates that one entity serves as the underlying physical foundation, mechanism, or substrate that gives rise to or supports the properties, behavior, or existence of another entity.
-
C.
formsArcOf
Indicates that one entity curves around or spans between points so as to create an arc in relation to another entity.
-
D.
physicalOrigin
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
-
E.
isPhysicalArtifact
Indicates that the subject is a tangible, man-made object that physically exists in the real world.
- F. None of above. chosen
Provenance (4 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51c2b9bc81909a4ce91792294d1c |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca9d07eb08190866eb15333386dfa |
completed | April 1, 2026, 5:14 a.m. |
Created at: March 30, 2026, 7:47 p.m.