Triple
T7572540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulidae |
E179277
|
entity |
| Predicate | typicalLengthRange |
P18065
|
FINISHED |
| Object | about 8 to 11 centimeters |
—
|
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: about 8 to 11 centimeters | Statement: [Regulidae, typicalLengthRange, about 8 to 11 centimeters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLengthRange Context triple: [Regulidae, typicalLengthRange, about 8 to 11 centimeters]
-
A.
typicalLength
chosen
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
B.
typicalTrackLengthRange
Indicates the usual minimum and maximum lengths that a track associated with something tends to fall between.
-
C.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
D.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
E.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f94710a0819094508356b8d610ab |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.