Triple
T18032098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Maze |
E431415
|
entity |
| Predicate | politicalStatusIssue |
P14210
|
FINISHED |
| Object | special category status |
—
|
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: special category status | Statement: [the Maze, politicalStatusIssue, special category status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusIssue Context triple: [the Maze, politicalStatusIssue, special category status]
-
A.
politicalStatusContext
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
-
B.
politicalIssueIn
chosen
Indicates that a political issue is relevant to, occurs within, or is associated with a particular geographic or political region.
-
C.
politicalStatusRepresented
Indicates that an entity’s political status is expressed, symbolized, or officially represented by another entity.
-
D.
politicalStatusVariation
Indicates a change or difference in an entity’s political status over time or across contexts.
-
E.
supportedPoliticalStatus
Indicates that one entity endorsed, favored, or advocated for a particular political status or position of another entity.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be36724c8190aeae7444365a0851 |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.