Triple
T26970374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burrs |
E679298
|
entity |
| Predicate | detachesWhen |
P107015
|
FINISHED |
| Object | Clothing is handled |
—
|
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: Clothing is handled | Statement: [Burrs, detachesWhen, Clothing is handled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detachesWhen Context triple: [Burrs, detachesWhen, Clothing is handled]
-
A.
canDetach
chosen
Indicates that one entity is able to be separated or removed from another entity or from a larger whole.
-
B.
hasDetachment
Indicates that an entity is separated, disconnected, or removed from another entity or its original position.
-
C.
vanishesWhen
Indicates that one entity ceases to exist, be visible, or be present whenever a specified condition involving another entity holds.
-
D.
relatedToDetachment
Indicates a relationship in which one entity is associated with the act, state, or process of separating, disengaging, or being removed from another entity or context.
-
E.
separatedUntil
Indicates that two entities remain apart or not in contact up to a specified time or condition.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6212454348190905c6132f6191e76 |
completed | May 2, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:38 a.m.