Triple
T26446827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearson correlation coefficient |
E665236
|
entity |
| Predicate | neutralValue |
P160760
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Pearson correlation coefficient, neutralValue, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neutralValue Context triple: [Pearson correlation coefficient, neutralValue, 0]
-
A.
neutralized
Indicates that one entity has rendered another entity ineffective, harmless, or no longer able to exert its intended effect.
-
B.
neutralAttackFeature
Indicates that an entity has the capability to perform an attack that is neutral, i.e., not aligned with any particular side, type, or affinity.
-
C.
usesNeutral
Indicates that one entity employs or applies something in a neutral, unbiased, or non-aligned manner toward another entity or context.
-
D.
neutralSiteState
Indicates that a site or location is in a neutral, non-aligned, and non-active state with respect to the relevant interaction or conflict.
-
E.
isNeutralAbout
Indicates that one entity has no strong positive or negative opinion, preference, or stance toward another entity or subject.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61262052c8190957e30216b5acd53 |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 27, 2026, 12:02 a.m.