Triple
T14931808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentinosaurus huinculensis |
E372282
|
entity |
| Predicate | specificEpithetHonours |
P15352
|
FINISHED |
| Object | the town of Plaza Huincul |
—
|
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: the town of Plaza Huincul | Statement: [Argentinosaurus huinculensis, specificEpithetHonours, the town of Plaza Huincul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specificEpithetHonours Context triple: [Argentinosaurus huinculensis, specificEpithetHonours, the town of Plaza Huincul]
-
A.
honouredInTaxon
Indicates that an organism or taxonomic group is named in honor of a particular person, entity, or concept.
-
B.
speciesEponym
chosen
Indicates that a species is named in honor of a particular person or entity.
-
C.
honorificEponym
Indicates that one entity serves as an honorific namesake for another, typically recognizing or commemorating the person or entity in whose honor something is named.
-
D.
isNamedFor
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
E.
isNamedForEponymRole
Indicates that one entity bears a name derived from another entity that serves as its eponym or namesake.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64550dc8190ba44120df00ba498 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:36 a.m.