Triple
T1686018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Platonic solids |
E36442
|
entity |
| Predicate | areAll |
P24187
|
FINISHED |
| Object | vertex-transitive polyhedra |
—
|
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: vertex-transitive polyhedra | Statement: [Platonic solids, areAll, vertex-transitive polyhedra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areAll Context triple: [Platonic solids, areAll, vertex-transitive polyhedra]
-
A.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
-
B.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
C.
alsoHolds
chosen
Indicates that a condition, property, or relation that applies in one context or case simultaneously applies in another context or case.
-
D.
wasAmong
Indicates that an entity belonged to, was included in, or was part of a particular group, set, or collection.
-
E.
availableWith
Indicates that one entity can be obtained, accessed, or used in conjunction with 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.