Triple
T2384486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OPENSTEP |
E46387
|
entity |
| Predicate | supportsObjectPersistence |
P31904
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [OPENSTEP, supportsObjectPersistence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsObjectPersistence Context triple: [OPENSTEP, supportsObjectPersistence, true]
-
A.
supportsPersistence
chosen
Indicates that one entity enables or provides the capability for another entity’s data or state to be stored and retained over time.
-
B.
storesObjectsAs
Indicates that one entity keeps or maintains other entities within it as stored items or contents.
-
C.
persistsAfter
Indicates that one state, condition, or effect continues to exist after a specified event, time point, or other state has occurred or ended.
-
D.
persistence
Indicates a continued or repeated existence, occurrence, or effort of something over time despite potential changes or obstacles.
-
E.
supportsPersistentPreallocation
Indicates that an entity is capable of maintaining resources or allocations in advance over time, rather than allocating them only on demand.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc7bc87d0819090cd9d19d748bcc3 |
completed | March 7, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69abc59f73f08190924a36d7d475d8f4 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.