Triple
T5477991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restricted Data |
E123401
|
entity |
| Predicate | mayBeTransclassifiedTo |
P22031
|
FINISHED |
| Object | Formerly Restricted Data |
—
|
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: Formerly Restricted Data | Statement: [Restricted Data, mayBeTransclassifiedTo, Formerly Restricted Data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeTransclassifiedTo Context triple: [Restricted Data, mayBeTransclassifiedTo, Formerly Restricted Data]
-
A.
reclassifiedAs
chosen
Indicates that an entity’s classification or category has been changed from a previous one to a new one.
-
B.
isSometimesClassifiedAs
Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
-
C.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
D.
reclassifiedBy
Indicates that an entity’s classification or category has been changed by a specific agent or authority.
-
E.
mayBeTransferredIf
Indicates that something is allowed to be transferred from one party or context to another under certain conditions.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd92460f008190bf9d64ddd9c507a7 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.