Triple
T12645279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bottle Creek Mounds |
E302006
|
entity |
| Predicate | largestMoundHeight |
P87793
|
FINISHED |
| Object | approximately 45 feet |
—
|
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: approximately 45 feet | Statement: [Bottle Creek Mounds, largestMoundHeight, approximately 45 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestMoundHeight Context triple: [Bottle Creek Mounds, largestMoundHeight, approximately 45 feet]
-
A.
maximumMoundHeight
chosen
Indicates the greatest allowable or observed height of a mound relative to a specified reference or context.
-
B.
centralMoundHeight
Indicates the height measurement of a central mound relative to a defined reference level.
-
C.
highestPyramidHeight
Indicates the maximum vertical height reached by any pyramid in a given context or set.
-
D.
archaeologicalMoundName
Indicates the specific name assigned to an archaeological mound in which something is located, associated, or from which it originates.
-
E.
numberOfMounds
Indicates the quantitative relationship specifying how many mounds are associated with a given entity or context.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:17 p.m.