Triple
T7192451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcomb–Benford law |
E167726
|
entity |
| Predicate | predictsProbabilityOfLeadingDigit6 |
P12745
|
FINISHED |
| Object | approximately 0.067 |
—
|
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: approximately 0.067 | Statement: [Newcomb–Benford law, predictsProbabilityOfLeadingDigit6, approximately 0.067]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predictsProbabilityOfLeadingDigit6 Context triple: [Newcomb–Benford law, predictsProbabilityOfLeadingDigit6, approximately 0.067]
-
A.
digitForSix
Indicates that something is the digit used to represent the number six.
-
B.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
C.
definesProbability
chosen
Indicates that one entity specifies or assigns the probability value associated with another entity or event.
-
D.
digitForSeven
Indicates that something serves as the digit representation specifically for the number seven.
-
E.
logarithmBaseDetermines
Indicates that the chosen base of a logarithm determines how a quantity is expressed or scaled in logarithmic terms.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e901ea1481908a9e44f96dd4b553 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.