Triple
T28622041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyakov action |
E724408
|
entity |
| Predicate | isUsedToDerive |
P49064
|
FINISHED |
| Object | string scattering amplitudes |
—
|
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 scattering amplitudes | Statement: [Polyakov action, isUsedToDerive, string scattering amplitudes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedToDerive Context triple: [Polyakov action, isUsedToDerive, string scattering amplitudes]
-
A.
isUsedForDerivatives
Indicates that something serves as a basis, input, or underlying component for creating or calculating derivatives.
-
B.
canDerive
Indicates that one entity can be logically or procedurally obtained, inferred, or produced from another entity based on defined rules or transformations.
-
C.
isUsedToCompute
chosen
Indicates that one entity serves as an input, basis, or resource for performing a calculation or deriving a result about another entity.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
isBelievedToBeUsedFor
Indicates that something is thought or assumed to serve a particular purpose or function, without certainty.
- 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_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:34 a.m.