Triple
T37163920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VobSub |
E920744
|
entity |
| Predicate | storesTimingIn |
P188502
|
FINISHED |
| Object | IDX file |
—
|
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: IDX file | Statement: [VobSub, storesTimingIn, IDX file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesTimingIn Context triple: [VobSub, storesTimingIn, IDX file]
-
A.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
-
B.
storesPackageStatusIn
Indicates that an entity records or maintains the status information of a package within a particular storage location or system.
-
C.
storesIndexesIn
Indicates that one entity maintains and holds index data within another storage entity or system.
-
D.
store
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
E.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:15 p.m.