Triple
T4979739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Office encryption (legacy) |
E111853
|
entity |
| Predicate | passwordSpace |
P60769
|
FINISHED |
| Object | limited effective key space |
—
|
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: limited effective key space | Statement: [Microsoft Office encryption (legacy), passwordSpace, limited effective key space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passwordSpace Context triple: [Microsoft Office encryption (legacy), passwordSpace, limited effective key space]
-
A.
formsPass
Indicates that one entity successfully completes or satisfies a required form or set of forms.
-
B.
hasPass
Indicates that an entity possesses or has been granted a pass, such as a ticket, permit, or authorization to access something.
-
C.
isWrittenWithSpace
Indicates that something is written or represented with spaces separating its components or elements.
-
D.
passType
Indicates the type or category of a pass that is involved in or assigned within the relationship between entities.
-
E.
performanceSpaceType
Indicates the specific kind or category of space in which a performance or event takes place.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:33 p.m.