Triple
T4426997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dana |
E95232
|
entity |
| Predicate | roleInNomenclature |
P55932
|
FINISHED |
| Object | original describer of Antarctic krill |
—
|
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: original describer of Antarctic krill | Statement: [Dana, roleInNomenclature, original describer of Antarctic krill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInNomenclature Context triple: [Dana, roleInNomenclature, original describer of Antarctic krill]
-
A.
notationRole
Indicates a role or function that an entity plays specifically within a system of notation or symbolic representation.
-
B.
nomenclaturalCode
Indicates the formal set of naming rules or code under which an entity’s scientific or taxonomic name is established or governed.
-
C.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
-
D.
conceptualRole
Indicates the functional or semantic role that one concept plays in relation to another within a conceptual structure or system.
-
E.
isNamedForEponymRole
Indicates that one entity bears a name derived from another entity that serves as its eponym or namesake.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554fb28081909018eaecc0c5c230 |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:30 p.m.