Triple
T27084136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RN6 |
E685987
|
entity |
| Predicate | classificationChangeType |
P38005
|
FINISHED |
| Object | administrative reclassification |
—
|
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: administrative reclassification | Statement: [RN6, classificationChangeType, administrative reclassification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationChangeType Context triple: [RN6, classificationChangeType, administrative reclassification]
-
A.
classificationChange
Indicates a change in the category, type, or status under which an entity is classified.
-
B.
classificationChangeContext
Indicates the circumstances or factors under which an entity’s classification is altered from one category or level to another.
-
C.
classificationMayChange
Indicates that the classification or category assigned to an entity is not fixed and can be updated or altered over time.
-
D.
changeType
chosen
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
E.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 8:36 a.m.