Triple
T18175971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilopoda |
E435160
|
entity |
| Predicate | legPairsRange |
P70462
|
FINISHED |
| Object | from15ToMoreThan170Pairs |
—
|
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: from15ToMoreThan170Pairs | Statement: [Chilopoda, legPairsRange, from15ToMoreThan170Pairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legPairsRange Context triple: [Chilopoda, legPairsRange, from15ToMoreThan170Pairs]
-
A.
legspanRange
Indicates the range of leg span values associated with an entity, typically specifying minimum and maximum leg span measurements.
-
B.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
-
C.
legs
chosen
Indicates that an entity possesses legs, specifying the presence or number of leg-like appendages associated with it.
-
D.
legOrder
Indicates the sequential position or ordering of a specific leg within a multi-leg structure, process, or route.
-
E.
shoulderHeightRange
Indicates the range of vertical height measured from the ground to an entity’s shoulders.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df59bf3881909adc28cacbe9cb39 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.