Triple
T8715211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haferlschuhe |
E206875
|
entity |
| Predicate | hasClosure |
P84050
|
FINISHED |
| Object | laces |
—
|
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: laces | Statement: [Haferlschuhe, hasClosure, laces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClosure Context triple: [Haferlschuhe, hasClosure, laces]
-
A.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
B.
subjectToClosure
Indicates that an entity is liable or scheduled to be closed, discontinued, or shut down under certain conditions or plans.
-
C.
conditionAfterClosure
Indicates the state or circumstances that exist after a process, event, or entity has been formally closed or concluded.
-
D.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
E.
closureAffected
Indicates that an entity is impacted or influenced by the closing or termination of another entity, process, or resource.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd807cc819090b58caf285b397a |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c40c54819093d174a4203f9515 |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:35 p.m.