Triple
T23628336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capture of Oaxaca (1812) |
E583533
|
entity |
| Predicate | typeOfLocationCaptured |
P153331
|
FINISHED |
| Object | colonial city |
—
|
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: colonial city | Statement: [Capture of Oaxaca (1812), typeOfLocationCaptured, colonial city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLocationCaptured Context triple: [Capture of Oaxaca (1812), typeOfLocationCaptured, colonial city]
-
A.
captureType
Indicates the manner or method by which something is captured, recorded, or acquired in the context of the relationship.
-
B.
currentLocationType
Indicates the type or category of place where an entity is currently located.
-
C.
capturedUsing
Indicates that something was recorded, obtained, or documented by means of a specified tool, method, or device.
-
D.
capturedIn
Indicates that one entity was taken prisoner, seized, or otherwise brought under control within the context, location, or event represented by another entity.
-
E.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e5ae80819085c417e8d81b74ad |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f138b8c9248190b059bc38a9a50958 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 17, 2026, 6:46 p.m.