Triple
T15340021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Payaya language |
E366765
|
entity |
| Predicate | associatedTribeLocation |
P118180
|
FINISHED |
| Object | present-day San Antonio, Texas |
—
|
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: present-day San Antonio, Texas | Statement: [Payaya language, associatedTribeLocation, present-day San Antonio, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTribeLocation Context triple: [Payaya language, associatedTribeLocation, present-day San Antonio, Texas]
-
A.
associatedTribeActivity
Indicates a relationship where a specific activity is linked to, practiced by, or characteristic of a particular tribe.
-
B.
addressesTribes
Indicates that an entity formally communicates with, speaks to, or directs statements or messages toward one or more tribes.
-
C.
hasTribalHeadquartersNearby
Indicates that the subject entity is located close to the tribal headquarters of a Native nation or tribe.
-
D.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
E.
tribeInteractedWith
Indicates that a tribe has engaged in some form of interaction or contact with another entity.
- F. None of above. chosen
Provenance (4 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e12eb7c8190944a260aa1aa9156 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:17 a.m.