Triple
T27504438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluvianellidae |
E694242
|
entity |
| Predicate | relativeSizeWithinOrder |
P8238
|
FINISHED |
| Object | small bird family |
—
|
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: small bird family | Statement: [Pluvianellidae, relativeSizeWithinOrder, small bird family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSizeWithinOrder Context triple: [Pluvianellidae, relativeSizeWithinOrder, small bird family]
-
A.
relativeSizeWithinSite
Indicates the comparative size relationship of one entity to another within the same site or local context.
-
B.
relativeSizeInFleet
Indicates the comparative size or capacity of an entity relative to other entities within the same fleet.
-
C.
relativeSizeOnTethys
Indicates how the size of one entity compares to another specifically in the context of Tethys.
-
D.
hasRelativeSize
chosen
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
-
E.
classWithinOrder
Indicates that a biological class is a subordinate taxonomic rank contained within a particular order.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
Created at: April 27, 2026, 1:13 p.m.