Triple
T17202814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Juan Sacatepéquez Kaqchikel |
E417519
|
entity |
| Predicate | hasPersonMarkers |
P2130
|
FINISHED |
| Object | set A and set B agreement markers |
—
|
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: set A and set B agreement markers | Statement: [San Juan Sacatepéquez Kaqchikel, hasPersonMarkers, set A and set B agreement markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersonMarkers Context triple: [San Juan Sacatepéquez Kaqchikel, hasPersonMarkers, set A and set B agreement markers]
-
A.
hasMarker
chosen
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
B.
hasPerson
Indicates that an entity is associated with or includes a specific person.
-
C.
hasPersona
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
-
D.
hasMeasurementMarkings
Indicates that one entity bears visible measurement indicators or scale markings on its surface for quantifying something.
-
E.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42db11fc881908291bf29cc740e09 |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.