Triple
T31898254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coulomb potential |
E814348
|
entity |
| Predicate | longRange |
P161128
|
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, longRange, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longRange Context triple: [Coulomb potential, longRange, true]
-
A.
isLongRange
chosen
Indicates that the relationship or action involves operating effectively over a large or extended distance.
-
B.
longLived
Indicates that an entity has a lifespan or duration of existence significantly longer than what is typical or expected in its context.
-
C.
longType
Indicates that something has a length-related classification or is characterized by being of extended duration or distance.
-
D.
longDistanceTrail
Indicates that a trail or route spans a considerable distance, typically intended for extended or multi-day travel.
-
E.
longDistanceService
Indicates that a service operates over large geographic distances, typically connecting locations that are far apart rather than nearby.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b166b4788190997dc7d7b865a428 |
completed | May 3, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:59 p.m.