Triple
T27787399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balaenicipitidae |
E700996
|
entity |
| Predicate | scientificNameOfRepresentativeSpecies |
P167334
|
FINISHED |
| Object | Balaeniceps rex |
—
|
NE NERFINISHED |
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: Balaeniceps rex | Statement: [Balaenicipitidae, scientificNameOfRepresentativeSpecies, Balaeniceps rex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scientificNameOfRepresentativeSpecies Context triple: [Balaenicipitidae, scientificNameOfRepresentativeSpecies, Balaeniceps rex]
-
A.
commonNameOfNotableSpecies
Indicates that the subject is a commonly used vernacular or everyday name for a notable or well-known biological species.
-
B.
scientificName
Indicates the formal taxonomic name assigned to an organism according to scientific naming conventions.
-
C.
speciesForm
Indicates that one entity is a specific biological form, variant, or manifestation of a species represented by another entity.
-
D.
namedTaxon
Indicates that an entity is identified as, or associated with, a particular taxonomic name.
-
E.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 27, 2026, 5:26 p.m.