Triple
T15445213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauropoda |
E370004
|
entity |
| Predicate | estimatedMaxLength |
P34006
|
FINISHED |
| Object | over 30 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: over 30 meters | Statement: [Sauropoda, estimatedMaxLength, over 30 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedMaxLength Context triple: [Sauropoda, estimatedMaxLength, over 30 meters]
-
A.
hasMaxLengthApprox
chosen
Indicates that something has a maximum length that is approximately equal to a specified value, allowing for some tolerance or imprecision.
-
B.
hasMaximumLength
Indicates that there is an upper limit on the length or size of something, beyond which it cannot extend.
-
C.
maximumSegmentLength
Indicates the greatest allowable or observed length of a segment within a given context or structure.
-
D.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
-
E.
estimatedOriginalLength
Indicates the approximated or inferred length that something originally had before any changes, damage, or loss.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef666e08190a02a01a676306ab9 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.