Triple
T33275997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chacmultún |
E851907
|
entity |
| Predicate | hasBuildingGroup |
P185343
|
FINISHED |
| Object | acropolis-type groups |
—
|
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: acropolis-type groups | Statement: [Chacmultún, hasBuildingGroup, acropolis-type groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingGroup Context triple: [Chacmultún, hasBuildingGroup, acropolis-type groups]
-
A.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
B.
hasBuildingOrganization
Indicates that an organization is associated with or occupies a particular building.
-
C.
hasBuildingClass
Indicates that a building is categorized as belonging to a specific building class or type.
-
D.
hasBuildingFrom
Indicates a relationship where a location or site possesses or includes a building that originates from, or was constructed in, a specified time period, source, or context.
-
E.
hasBuildingComponent
Indicates that one entity includes, contains, or is composed of another entity as a physical building component.
- 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 1, 2026, 1:32 a.m.