Triple
T38202656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Saca |
E1009108
|
entity |
| Predicate | regionAtTheTime |
P121592
|
FINISHED |
| Object | Provincia de Nuevo México |
—
|
NE NERFINISHED |
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: Provincia de Nuevo México | Statement: [El Saca, regionAtTheTime, Provincia de Nuevo México]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionAtTheTime Context triple: [El Saca, regionAtTheTime, Provincia de Nuevo México]
-
A.
territoryAtTime
Indicates that a specified territory is associated with or held by an entity during a particular time or time interval.
-
B.
administrativeAreaAtTime
Indicates that an entity was located within or belonged to a specific administrative area during a specified time period.
-
C.
locatedAtTime
chosen
Indicates that a location relationship holds during a specific time or time interval.
-
D.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
E.
regionDuringBR
Indicates that a region exists or is valid specifically during a defined base or reference time interval (BR).
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a008ac37dc081908d360574912f40ec |
completed | May 10, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_6a008a67d73881909855ab4cfca3c399 |
completed | May 10, 2026, 1:38 p.m. |
Created at: May 3, 2026, 4:30 p.m.