Triple
T27273824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yax Kʼukʼ Moʼ |
E688129
|
entity |
| Predicate | inferredOrigin |
P3654
|
FINISHED |
| Object | central Petén region (probable) |
—
|
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: central Petén region (probable) | Statement: [Yax Kʼukʼ Moʼ, inferredOrigin, central Petén region (probable)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inferredOrigin Context triple: [Yax Kʼukʼ Moʼ, inferredOrigin, central Petén region (probable)]
-
A.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
B.
indirectOrigin
Indicates that one entity originates from or is derived through one or more intermediate sources or processes from another entity, rather than directly.
-
C.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
D.
physicalOrigin
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
-
E.
inferredType
Indicates that an entity has a type or category that has been deduced or derived rather than explicitly stated.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62725b5d48190b5defc0995e6a481 |
completed | May 2, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:01 a.m.