Triple
T18629562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q-learning |
E455376
|
entity |
| Predicate | usesMaxOperatorOver |
P132460
|
FINISHED |
| Object | next-state action values |
—
|
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: next-state action values | Statement: [Q-learning, usesMaxOperatorOver, next-state action values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMaxOperatorOver Context triple: [Q-learning, usesMaxOperatorOver, next-state action values]
-
A.
usesOperatorPosition
Indicates that one entity occupies or is assigned to the role of an operator within a particular position or context.
-
B.
isMaximumWhen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
-
C.
largestOperator
Indicates that the subject is the operator with the greatest size, capacity, or scale among a specified set of operators.
-
D.
usedByOperator
Indicates that something is utilized or operated by a particular operator or operating entity.
-
E.
hasMajorOperator
Indicates that an entity is primarily operated, managed, or run by a specified main operator or organization.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f06f4a081909b64f33814577488 |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:46 a.m.