Triple
T9253095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etowah Indian Mounds |
E222373
|
entity |
| Predicate | maximumMoundHeight |
P87793
|
FINISHED |
| Object | approximately 19 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: approximately 19 meters | Statement: [Etowah Indian Mounds, maximumMoundHeight, approximately 19 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumMoundHeight Context triple: [Etowah Indian Mounds, maximumMoundHeight, approximately 19 meters]
-
A.
centralMoundHeight
Indicates the height measurement of a central mound relative to a defined reference level.
-
B.
highestPyramidHeight
Indicates the maximum vertical height reached by any pyramid in a given context or set.
-
C.
numberOfMounds
Indicates the quantitative relationship specifying how many mounds are associated with a given entity or context.
-
D.
maximumNumber
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
E.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b0789481908e8e44ebf1b3c713 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:31 p.m.