Triple
T4979759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Office encryption (legacy) |
E111853
|
entity |
| Predicate | statusInModernOffice |
P50004
|
FINISHED |
| Object | legacy compatibility only |
—
|
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: legacy compatibility only | Statement: [Microsoft Office encryption (legacy), statusInModernOffice, legacy compatibility only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInModernOffice Context triple: [Microsoft Office encryption (legacy), statusInModernOffice, legacy compatibility only]
-
A.
worksWithOffice
Indicates that an entity collaborates or is professionally associated with a particular office or office-based organization.
-
B.
officeState
chosen
Indicates the current operational or functional status of an office (e.g., open, closed, active, inactive) at a given time.
-
C.
officeUnder
Indicates that one office is subordinate to, managed by, or organizationally within the authority of another office.
-
D.
controlledOffice
Indicates that one entity has authority over, manages, or directs the operations of a particular office or administrative location.
-
E.
inOfficeDuring
Indicates that an entity holds or occupies an office or position throughout a specified time period.
- 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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.