Triple
T28622027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyakov action |
E724408
|
entity |
| Predicate | containsParameter |
P4452
|
FINISHED |
| Object | string tension T |
—
|
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 tension T | Statement: [Polyakov action, containsParameter, string tension T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsParameter Context triple: [Polyakov action, containsParameter, string tension T]
-
A.
hasParameter
chosen
Indicates that an entity is associated with a specific parameter that defines or constrains some aspect of its behavior, configuration, or characteristics.
-
B.
hasParameterization
Indicates that one entity serves as the specific parameterization or parameter-setting scheme used to define or configure another entity.
-
C.
hasParameterType
Indicates that a parameter in a function, method, or operation is associated with a specific data type.
-
D.
parameterLivesIn
Indicates that a given parameter or variable is associated with, resides within, or is scoped to a particular context, environment, or container.
-
E.
containsPass
Indicates that one entity includes or holds a valid pass or authorization credential within it.
- 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_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 28, 2026, 4:34 a.m.