Triple
T2556091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Management Data Warehouse |
E56732
|
entity |
| Predicate | dataCollectionMode |
P27468
|
FINISHED |
| Object | scheduled |
—
|
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: scheduled | Statement: [Management Data Warehouse, dataCollectionMode, scheduled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectionMode Context triple: [Management Data Warehouse, dataCollectionMode, scheduled]
-
A.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
B.
currentCollectionMethod
Indicates the method or process currently being used to collect something (such as data, payments, or materials) from an entity.
-
C.
modeType
chosen
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
-
D.
canCollect
Indicates that one entity has the ability or permission to gather, receive, or take possession of another entity.
-
E.
collectedThrough
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
- 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.