Triple
T16028869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Futalognkosaurus |
E388789
|
entity |
| Predicate | neckVertebrae |
P49300
|
FINISHED |
| Object | robust and tall neural spines |
—
|
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: robust and tall neural spines | Statement: [Futalognkosaurus, neckVertebrae, robust and tall neural spines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neckVertebrae Context triple: [Futalognkosaurus, neckVertebrae, robust and tall neural spines]
-
A.
neckVertebraeCount
Indicates the number of vertebrae present in the neck of an entity.
-
B.
neckJoint
Indicates a joint or connection located at or functioning as the neck between two body parts or structural elements.
-
C.
caudalSpineLocation
Indicates the anatomical position or region where the caudal (tail) spine is located on an organism.
-
D.
headMobility
Indicates the degree to which an entity’s head can move or be moved relative to its body.
-
E.
neckCharacteristic
chosen
Indicates that an entity has a specific attribute, feature, or quality related to its neck.
- 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_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. |
Created at: April 10, 2026, 4:56 a.m.