Triple
T10534766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaan |
E248534
|
entity |
| Predicate | exertedInfluenceOver |
P45664
|
FINISHED |
| Object | other Maya city-states |
—
|
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: other Maya city-states | Statement: [Kaan, exertedInfluenceOver, other Maya city-states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exertedInfluenceOver Context triple: [Kaan, exertedInfluenceOver, other Maya city-states]
-
A.
hasSignificantInfluenceIn
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
-
B.
hadInfluenceOn
chosen
Indicates that one entity affected, shaped, or contributed to the development, behavior, or characteristics of another entity.
-
C.
influencedPerson
Indicates that one entity has affected, shaped, or guided the thoughts, behavior, or development of another person.
-
D.
politicalInfluenceIn
Indicates that an entity exerts or holds political influence within a specified place, jurisdiction, or political context.
-
E.
hasEnduringInfluenceOn
Indicates that one entity exerts a lasting, long-term impact on another entity’s state, development, or behavior.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a1a754c8190b53f2df28a1dfef1 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:31 p.m.