Triple
T25210406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxfords |
E631668
|
entity |
| Predicate | hasTypicalClosure |
P144337
|
FINISHED |
| Object | shoelaces |
—
|
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: shoelaces | Statement: [Oxfords, hasTypicalClosure, shoelaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalClosure Context triple: [Oxfords, hasTypicalClosure, shoelaces]
-
A.
hasClosure
Indicates that one entity possesses, defines, or is associated with the closure (completion or boundary-encompassing form) of another entity or operation.
-
B.
typicalClosures
chosen
Indicates that one entity represents the standard or commonly used ways in which the other entity is completed, terminated, or brought to a close.
-
C.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
D.
subjectToClosure
Indicates that an entity is liable or scheduled to be closed, discontinued, or shut down under certain conditions or plans.
-
E.
hasTypicalAccess
Indicates that one entity normally or customarily has the ability, permission, or means to access or use another entity.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 12:58 p.m.