Triple
T11961735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snell envelope |
E284683
|
entity |
| Predicate | roleInControl |
P268
|
FINISHED |
| Object | tool in stochastic control problems with stopping |
—
|
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: tool in stochastic control problems with stopping | Statement: [Snell envelope, roleInControl, tool in stochastic control problems with stopping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInControl Context triple: [Snell envelope, roleInControl, tool in stochastic control problems with stopping]
-
A.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
D.
roleInAdministration
Indicates that an entity holds a specific position or function within an administrative structure or governing body.
-
E.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037848f481908276716675464464 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.