Triple
T11905002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thepla |
E283250
|
entity |
| Predicate | canBeStoredFor |
P102162
|
FINISHED |
| Object | several days |
—
|
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: several days | Statement: [Thepla, canBeStoredFor, several days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeStoredFor Context triple: [Thepla, canBeStoredFor, several days]
-
A.
canExpire
Indicates that the subject has the property or status of being able to end, lapse, or become invalid after a certain time or condition is met.
-
B.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
-
C.
storageOption
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
D.
canBeReconstituted
Indicates that something has the capacity to be restored or returned to a prior or functional state, typically after being separated, dissolved, or broken down.
-
E.
storesForPurpose
Indicates that one entity stores or keeps another entity specifically in order to fulfill a particular purpose or intended use.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e525460c81909d855048d9c799bf |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.