Triple
T5891384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AX |
E130995
|
entity |
| Predicate | regionTypeRepresented |
P59369
|
FINISHED |
| Object | autonomous region |
—
|
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: autonomous region | Statement: [AX, regionTypeRepresented, autonomous region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionTypeRepresented Context triple: [AX, regionTypeRepresented, autonomous region]
-
A.
regionType
Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
-
B.
regionRepresentation
Indicates that one entity serves as a representation, model, or depiction of a specific geographic or spatial region associated with another entity.
-
C.
typeOfAreaRepresented
chosen
Indicates that one entity specifies the kind or category of area that another entity represents.
-
D.
regionTypeEast
Indicates that one region is classified as being of a certain type specifically in the eastern part of a larger area or reference frame.
-
E.
regionTypeWest
Indicates that one region is of a specified type and is located to the west of another region.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.