Triple
T38631565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seth Thornton |
E937467
|
entity |
| Predicate | locationOfAmbush |
P206589
|
FINISHED |
| Object | near the Rio Grande |
—
|
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: near the Rio Grande | Statement: [Seth Thornton, locationOfAmbush, near the Rio Grande]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfAmbush Context triple: [Seth Thornton, locationOfAmbush, near the Rio Grande]
-
A.
ambushParticipant
Indicates that an entity takes part in an ambush, either as an attacker or as a target within that ambush event.
-
B.
ambushStrategy
Indicates a planned tactic in which one party conceals its presence or intentions to surprise and attack another party.
-
C.
climaxLocation
Indicates the place or setting where the most intense or pivotal moment of an event, narrative, or process occurs.
-
D.
rescuedLocation
Indicates the place where a rescue action occurred or from which someone or something was rescued.
-
E.
exileLocation
Indicates the place or destination to which an entity is sent or kept in exile.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.