Triple
T24816892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rhombicosidodecahedron |
E620946
|
entity |
| Predicate | hasDiscoveryAttribution |
P53154
|
FINISHED |
| Object | Archimedes of Syracuse |
—
|
NE NERFINISHED |
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: Archimedes of Syracuse | Statement: [rhombicosidodecahedron, hasDiscoveryAttribution, Archimedes of Syracuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscoveryAttribution Context triple: [rhombicosidodecahedron, hasDiscoveryAttribution, Archimedes of Syracuse]
-
A.
attributedDiscovery
chosen
Indicates that the discovery of something is credited or assigned to a particular agent or entity.
-
B.
hasDiscoveryStatus
Indicates the current state or phase of discovery or identification associated with an entity.
-
C.
hasDiscovered
Indicates that one entity has found, detected, or uncovered the existence, presence, or truth of another entity or phenomenon.
-
D.
hasDiscoveryFeature
Indicates that an entity includes or supports a capability for discovering, finding, or surfacing other relevant entities, items, or information.
-
E.
hasDiscoveryType
Indicates the specific manner, method, or category by which something was discovered.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 18, 2026, 5:03 a.m.