Triple
T28622050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyakov action |
E724408
|
entity |
| Predicate | isStandardToolIn |
P33439
|
FINISHED |
| Object | string perturbation theory |
—
|
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: string perturbation theory | Statement: [Polyakov action, isStandardToolIn, string perturbation theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandardToolIn Context triple: [Polyakov action, isStandardToolIn, string perturbation theory]
-
A.
isToolIn
Indicates that a tool is located within or contained inside a specified space, container, or context.
-
B.
usesToolType
chosen
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
C.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
D.
usesToolFor
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
-
E.
isStandardOn
Indicates that a particular feature, option, or component is included by default as part of another item, rather than being optional or extra.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 4:34 a.m.