Triple
T37665201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End rod |
E937804
|
entity |
| Predicate | canBeBrokenByHand |
P200313
|
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: [End rod, canBeBrokenByHand, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBrokenByHand Context triple: [End rod, canBeBrokenByHand, true]
-
A.
toolToBreak
Indicates that one entity is used as a tool or instrument to break, damage, or destroy another entity.
-
B.
willBreakFreeDuring
Indicates that an entity is expected to escape or become free from another entity or constraint during a specified time or event.
-
C.
dropsItselfWhenBroken
Indicates that when the object is broken, it produces and drops an instance of itself as a collectible or item.
-
D.
breaksDownWhen
Indicates that one entity becomes nonfunctional, damaged, or fails when subjected to the presence, action, or conditions imposed by another entity.
-
E.
brokenOn
Indicates that an object or system ceased functioning or became damaged at a specific time or on a specific date.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69ff7fc715208190a8e4e2cc5aa72d2c |
completed | May 9, 2026, 6:41 p.m. |
Created at: May 3, 2026, 4:18 p.m.