Triple
T33887598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaan dynasty |
E868670
|
entity |
| Predicate | inferredEarlyCapital |
P66247
|
FINISHED |
| Object | Dzibanche |
—
|
NE NERFINISHED |
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: Dzibanche | Statement: [Kaan dynasty, inferredEarlyCapital, Dzibanche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inferredEarlyCapital Context triple: [Kaan dynasty, inferredEarlyCapital, Dzibanche]
-
A.
possibleCapital
chosen
Indicates that a location is a candidate or potential capital city of a given political or administrative entity.
-
B.
capitalizedOn
Indicates that one entity took advantage of, exploited, or made beneficial use of an opportunity, situation, or resource provided or created by another entity.
-
C.
hasLaterCapital
Indicates that one entity’s designation or establishment as a capital city occurred later in time than that of another entity.
-
D.
earlierCapitalAssociated
Indicates that one entity served as a capital city at an earlier time than the other associated capital entity.
-
E.
precededAsCapitalBy
Indicates that one capital city previously held the status of capital before being succeeded by another capital city.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.