Triple
T11725059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allosaurus |
E278741
|
entity |
| Predicate | maximumEstimatedLength |
P25800
|
FINISHED |
| Object | 10 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: 10 meters | Statement: [Allosaurus, maximumEstimatedLength, 10 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumEstimatedLength Context triple: [Allosaurus, maximumEstimatedLength, 10 meters]
-
A.
maximumSegmentLength
Indicates the greatest allowable or observed length of a segment within a given context or structure.
-
B.
hasMaxLengthApprox
Indicates that something has a maximum length that is approximately equal to a specified value, allowing for some tolerance or imprecision.
-
C.
approximateLengthInMeters
chosen
Indicates the estimated or roughly measured length of something expressed in meters.
-
D.
approximateBlockLength
Indicates that one entity specifies or estimates the length of a block in an approximate or non-exact manner.
-
E.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d603cc8190b2e68d0bdd793362 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.