Triple
T27778874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monks Mound |
E699277
|
entity |
| Predicate | topStructure |
P163343
|
FINISHED |
| Object | possible temple |
—
|
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: possible temple | Statement: [Monks Mound, topStructure, possible temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topStructure Context triple: [Monks Mound, topStructure, possible temple]
-
A.
topStructure
chosen
Indicates that one structure occupies the highest or most superior position relative to other structures within a given system or hierarchy.
-
B.
rootStructure
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
-
C.
verticalStructure
Indicates a relationship where one entity is a structure that extends predominantly in the vertical direction relative to another reference or context.
-
D.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
E.
topLevel
Indicates that an entity occupies the highest or outermost level in a hierarchy, structure, or organizational arrangement, with no parent above it.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:08 p.m.