Triple
T12190139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf Coast theater of the Mexican–American War |
E290438
|
entity |
| Predicate | landEnvironment |
P9701
|
FINISHED |
| Object | coastal plains of eastern Mexico |
—
|
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: coastal plains of eastern Mexico | Statement: [Gulf Coast theater of the Mexican–American War, landEnvironment, coastal plains of eastern Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landEnvironment Context triple: [Gulf Coast theater of the Mexican–American War, landEnvironment, coastal plains of eastern Mexico]
-
A.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
-
B.
land
Indicates coming down from the air or a higher position to make contact with and settle on a surface.
-
C.
landscapeType
chosen
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
-
D.
territorialNature
Indicates a tendency of an entity to defend or assert control over a specific area or domain against others.
-
E.
Land
Indicates that an entity arrives onto and comes to rest on a surface or ground, typically from the air or another elevated position.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.