Triple
T321257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Actinopterygii |
E6419
|
entity |
| Predicate | includesSizeRange |
P12465
|
FINISHED |
| Object | from a few millimeters to several meters in length |
—
|
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: from a few millimeters to several meters in length | Statement: [Actinopterygii, includesSizeRange, from a few millimeters to several meters in length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSizeRange Context triple: [Actinopterygii, includesSizeRange, from a few millimeters to several meters in length]
-
A.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
B.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
C.
sizeIncreasedTo
Indicates that an entity’s size has changed and reached a specified larger value or magnitude.
-
D.
approximateSize
Indicates that one entity has a size that is roughly or approximately equal to the size of another entity.
-
E.
hasRelativeSize
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e946607081909c8b97473aaf8d1b |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea7d03a88190aab72e61d8673488 |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.