Triple
T13124322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wastek |
E311804
|
entity |
| Predicate | isGeographicallyIsolatedFrom |
P96091
|
FINISHED |
| Object | other Mayan languages |
—
|
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 Mayan languages | Statement: [Wastek, isGeographicallyIsolatedFrom, other Mayan languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGeographicallyIsolatedFrom Context triple: [Wastek, isGeographicallyIsolatedFrom, other Mayan languages]
-
A.
geographicallySeparatedFrom
chosen
Indicates that two places or regions are distinct and apart from each other in physical location or geographic space.
-
B.
isolatedBy
Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
-
C.
separatedFromContinent
Indicates that an entity is geographically detached or isolated from a main continental landmass.
-
D.
isIsolated
Indicates that an entity exists or occurs separately from others, without direct contact, interaction, or connection.
-
E.
separatedFromByLand
Indicates that two entities are divided or kept apart from each other by an intervening landmass.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819946808190b41335fb1054accd |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.