Triple
T25097119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sitio Conte |
E628618
|
entity |
| Predicate | siteFunction |
P81043
|
FINISHED |
| Object | ritual center |
—
|
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: ritual center | Statement: [Sitio Conte, siteFunction, ritual center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteFunction Context triple: [Sitio Conte, siteFunction, ritual center]
-
A.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
-
B.
supportFunction
Indicates that one entity provides assistance, resources, or functionality that enables or enhances the operation or effectiveness of another entity.
-
C.
functie
chosen
Indicates that one entity serves as a function, role, or operational purpose in relation to another entity.
-
D.
applicationSite
Indicates the location or surface where a substance, treatment, or action is applied to an entity.
-
E.
typeSite
Indicates that a site is classified as being of a particular type or category.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b9651481908d4d7584717f5c59 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:25 a.m.