Triple
T38095416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Percichthyidae |
E951229
|
entity |
| Predicate | includesSpeciesWithBodySize |
P73619
|
FINISHED |
| Object | large |
—
|
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: large | Statement: [Percichthyidae, includesSpeciesWithBodySize, large]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSpeciesWithBodySize Context triple: [Percichthyidae, includesSpeciesWithBodySize, large]
-
A.
includesTaxaWithBodyMassRange
Indicates that the subject encompasses or contains taxa whose body masses fall within a specified numerical range.
-
B.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
C.
hasLargeSpecies
chosen
Indicates that an entity possesses or includes at least one species that is considered large in size.
-
D.
includesSpeciesFrom
Indicates that one collection, group, or set contains one or more species that originate from or belong to another specified source or context.
-
E.
includesSpeciesWithDiet
Indicates that a group, area, or collection contains at least one species characterized by a specified type of diet.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.