Triple
T12724571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Executive Order No. 220 |
E304069
|
entity |
| Predicate | regionTypeCreated |
P64281
|
FINISHED |
| Object | special administrative 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: special administrative region | Statement: [Executive Order No. 220, regionTypeCreated, special administrative region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionTypeCreated Context triple: [Executive Order No. 220, regionTypeCreated, special administrative 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.
createdEntityType
chosen
Indicates the type or category of entity that was produced or brought into existence as a result of the creation action.
-
C.
placeCreated
Indicates that one entity is the location where another entity was created or came into existence.
-
D.
createdFeature
Indicates that one entity brought another entity into existence or caused it to be produced as a feature.
-
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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.