Triple
T25113233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Precolumbian Chiefdom Settlements with Stone Spheres of the Diquís |
E629052
|
entity |
| Predicate | stoneSphereArrangement |
P159077
|
FINISHED |
| Object | alignments |
—
|
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: alignments | Statement: [Precolumbian Chiefdom Settlements with Stone Spheres of the Diquís, stoneSphereArrangement, alignments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoneSphereArrangement Context triple: [Precolumbian Chiefdom Settlements with Stone Spheres of the Diquís, stoneSphereArrangement, alignments]
-
A.
cylinderArrangement
Indicates how multiple cylinders are positioned or organized relative to one another.
-
B.
stoneSphereWeightRange
Indicates the range of possible weights associated with a given stone sphere.
-
C.
სფერო
Indicates a general field, domain, or area within which something operates, applies, or is categorized.
-
D.
numberOfSpheres
Indicates the quantity of spheres associated with or contained by a given entity.
-
E.
sporeArrangement
Indicates how spores are positioned, grouped, or distributed relative to each other or to supporting structures.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 18, 2026, 6:27 a.m.