Triple
T31898245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coulomb potential |
E814348
|
entity |
| Predicate | isConservative |
P179528
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Coulomb potential, isConservative, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConservative Context triple: [Coulomb potential, isConservative, true]
-
A.
isConservativeOver
Indicates that one entity preserves or does not increase a certain property, measure, or effect when applied over or in relation to another entity.
-
B.
hasConservatism
Indicates that one entity possesses, exhibits, or is characterized by a tendency toward conservatism in behavior, beliefs, or practices.
-
C.
hasConservativeFaction
Indicates that an entity includes or is associated with a subgroup characterized by conservative views or positions.
-
D.
identifiesAsConservativeLineageTo
Indicates that one entity regards another as belonging to, or continuing, a conservative ideological or traditional lineage.
-
E.
hasMoreConservativeRegion
Indicates that one region is characterized by more conservative attributes, policies, or tendencies compared to another region.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 30, 2026, 11:59 p.m.