Triple
T20539711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nojpetén |
E504293
|
entity |
| Predicate | presentDayGeographicalContext |
P140470
|
FINISHED |
| Object | northern Guatemala |
—
|
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: northern Guatemala | Statement: [Nojpetén, presentDayGeographicalContext, northern Guatemala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayGeographicalContext Context triple: [Nojpetén, presentDayGeographicalContext, northern Guatemala]
-
A.
presentDayContext
Indicates that the relationship or action is situated in, or relevant to, the current time period or contemporary context.
-
B.
presentDayCityIs
Indicates that one entity is the current, modern-day city corresponding to or located at the place represented by the other entity.
-
C.
presentDayCityCountry
Indicates that a given city is located in a specified country in the present day.
-
D.
presentDayNear
Indicates that one entity is located a short distance from another in the present time or current context.
-
E.
presentDayCenter
Indicates that an entity currently serves as the central or primary focal point (e.g., administrative, cultural, or functional center) of another entity in the present day.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a290bd8c819091988f511fb5820b |
completed | April 20, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:37 a.m.