Triple
T15238549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giganotosaurus |
E364192
|
entity |
| Predicate | hasReconstructedSkullLength |
P117689
|
FINISHED |
| Object | about 1.6–1.8 meters |
—
|
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: about 1.6–1.8 meters | Statement: [Giganotosaurus, hasReconstructedSkullLength, about 1.6–1.8 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReconstructedSkullLength Context triple: [Giganotosaurus, hasReconstructedSkullLength, about 1.6–1.8 meters]
-
A.
estimatedNumberOfSkulls
Indicates the approximate count of skulls associated with an entity, based on estimation rather than an exact measurement.
-
B.
skeletonCompleteness
Indicates the degree to which an entity’s skeleton is present, intact, or fully preserved in relation to its expected complete form.
-
C.
cranialCapacity
Indicates the volume or size of the interior space of the skull that can house the brain.
-
D.
numberOfBonesRecovered
Indicates the count of bones that have been found and recovered in relation to a particular subject or event.
-
E.
skullUsage
Indicates how a skull is used, applied, or functionally involved in a particular context or activity.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007da7e988190925a9b67b8070bc7 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:12 a.m.