Triple
T37029506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujitsu ESPRIMO PCs |
E916447
|
entity |
| Predicate | lifecyclePolicy |
P104457
|
FINISHED |
| Object | stable platform for corporate rollouts |
—
|
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: stable platform for corporate rollouts | Statement: [Fujitsu ESPRIMO PCs, lifecyclePolicy, stable platform for corporate rollouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifecyclePolicy Context triple: [Fujitsu ESPRIMO PCs, lifecyclePolicy, stable platform for corporate rollouts]
-
A.
supportsLifecyclePolicies
chosen
Indicates that an entity enables or is compatible with the definition, application, and management of lifecycle policies over time.
-
B.
preservationPolicy
Indicates the rules or strategy governing how something is maintained, protected, and retained over time.
-
C.
archivePolicy
Indicates the rules or conditions governing how items are stored, retained, and managed in an archive.
-
D.
detentionPolicy
Indicates the rules or conditions under which individuals may be held in custody or confinement.
-
E.
expirationPolicy
Indicates the rules or conditions under which something becomes invalid, unusable, or no longer in effect after a certain time or event.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.