Triple
T9551444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kincaid Mounds |
E230429
|
entity |
| Predicate | primaryMoundType |
P89755
|
FINISHED |
| Object | platform mound |
—
|
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: platform mound | Statement: [Kincaid Mounds, primaryMoundType, platform mound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMoundType Context triple: [Kincaid Mounds, primaryMoundType, platform mound]
-
A.
moundColor
Indicates the color associated with a mound.
-
B.
centralMoundHeight
Indicates the height measurement of a central mound relative to a defined reference level.
-
C.
numberOfMounds
Indicates the quantitative relationship specifying how many mounds are associated with a given entity or context.
-
D.
archaeologicalMoundName
Indicates the specific name assigned to an archaeological mound in which something is located, associated, or from which it originates.
-
E.
hasArchaeologicalMound
Indicates that an entity possesses or contains an archaeological mound, i.e., a raised earthwork or mound of archaeological significance located on or within it.
- 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd991df7308190a56d95f195627513 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:02 p.m.