Triple
T16666358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cahitan |
E404991
|
entity |
| Predicate | hasMemberLanguage |
P7390
|
FINISHED |
| Object | Mayo |
E169485
|
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: Mayo | Statement: [Cahitan, hasMemberLanguage, Mayo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mayo Context triple: [Cahitan, hasMemberLanguage, Mayo]
-
A.
Mayo
Mayo is a surname most prominently associated with the American medical family that co-founded the Mayo Clinic.
-
B.
Mayo
Mayo is a parliamentary constituency represented in Dáil Éireann, the lower house of the Irish parliament, covering most of County Mayo in western Ireland.
-
C.
Mayo
Mayo is a given name most notably associated with American musician and visual artist Mayo Thompson, leader of the experimental rock band Red Krayola.
-
D.
Mayo
chosen
The Mayo are an Indigenous people of northwestern Mexico, primarily inhabiting the state of Sonora and known for their rich agricultural traditions and ceremonial dances.
-
E.
Mayo
Mayo is an Australian federal electoral division in South Australia, encompassing a mix of Adelaide Hills communities and regional areas.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9cd7ec819084aa9b2830874bf5 |
completed | April 18, 2026, 12:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a008a32988c8190a671a4cbd829047a |
completed | May 10, 2026, 1:37 p.m. |
Created at: April 10, 2026, 5:18 a.m.