Triple
T16028856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Futalognkosaurus |
E388789
|
entity |
| Predicate | holotypePreserves |
P121419
|
FINISHED |
| Object | most of vertebral column |
—
|
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: most of vertebral column | Statement: [Futalognkosaurus, holotypePreserves, most of vertebral column]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holotypePreserves Context triple: [Futalognkosaurus, holotypePreserves, most of vertebral column]
-
A.
holotypeStatus
Indicates that an entity serves as the designated holotype specimen on which the formal description and name of a taxon are based.
-
B.
holotypeSpecimenNumber
Indicates the identifying specimen number assigned to the holotype that formally defines a taxon in biological classification.
-
C.
holotypeRepository
Indicates the institution or collection where the designated holotype specimen of a taxon is stored or curated.
-
D.
holotypeFoundOnPropertyOf
Indicates that the holotype specimen of a taxon was discovered on land owned or controlled by the referenced property holder.
-
E.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e185879c10819080a18e24969b5a6d |
completed | April 17, 2026, 12:57 a.m. |
Created at: April 10, 2026, 4:56 a.m.