Triple
T13628331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oaxaca (state) |
E325645
|
entity |
| Predicate | hasArchaeologicalSite |
P1098
|
FINISHED |
| Object | Yagul |
E159837
|
NE 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: Yagul | Statement: [Oaxaca (state), hasArchaeologicalSite, Yagul]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yagul Context triple: [Oaxaca (state), hasArchaeologicalSite, Yagul]
-
A.
Yagul
chosen
Yagul is an important pre-Columbian archaeological site in Oaxaca, Mexico, known for its well-preserved Zapotec ruins and hilltop fortress.
-
B.
Yagüe
Yagüe is a Spanish surname most notably associated with Juan Yagüe, a prominent general during the Spanish Civil War.
-
C.
Echigoya
Echigoya was a pioneering Edo-period dry-goods store in Japan that evolved into what is now the Mitsukoshi department store chain.
-
D.
Gucun
Gucun is a town in Shanghai, China, known for giving its name to the large urban Gucun Park.
-
E.
Puyuma
Puyuma are an indigenous Austronesian ethnic group of southeastern Taiwan known for their distinct language, matrilineal social structure, and rich ceremonial traditions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbe9d803481908101def32817b0eb |
completed | April 12, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77fa895f081908f72a0746afeabed |
completed | May 3, 2026, 5:02 p.m. |
Created at: April 9, 2026, 9:51 p.m.