Triple
T24806891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rhombicuboctahedron |
E620678
|
entity |
| Predicate | canBeTruncatedFrom |
P153496
|
FINISHED |
| Object | cube |
—
|
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: cube | Statement: [rhombicuboctahedron, canBeTruncatedFrom, cube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeTruncatedFrom Context triple: [rhombicuboctahedron, canBeTruncatedFrom, cube]
-
A.
canBeTruncated
Indicates that something is capable of being shortened or cut off, typically by removing a portion from its end.
-
B.
isConsistentTruncationOf
chosen
Indicates that one entity is a truncated version of another in a way that preserves the original structure or properties up to the point of truncation.
-
C.
canBeStrippedFor
Indicates that one entity is capable of having parts or layers removed in order to benefit, prepare, or expose another entity.
-
D.
canBeStripped
Indicates that one entity is capable of having an outer layer, covering, or component removed from it.
-
E.
canBeRemovedBy
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:50 a.m.