Triple
T2556090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Management Data Warehouse |
E56732
|
entity |
| Predicate | dataRetention |
P12561
|
FINISHED |
| Object | configurable |
—
|
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: configurable | Statement: [Management Data Warehouse, dataRetention, configurable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRetention Context triple: [Management Data Warehouse, dataRetention, configurable]
-
A.
retentionMethod
Indicates the method or strategy used to retain or keep something (such as data, customers, or resources) over time.
-
B.
preservationPolicy
chosen
Indicates the rules or strategy governing how something is maintained, protected, and retained over time.
-
C.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
-
D.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.