Triple
T7192480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcomb–Benford law |
E167726
|
entity |
| Predicate | typicalDatasetCondition |
P72526
|
FINISHED |
| Object | data spanning several orders of magnitude |
—
|
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: data spanning several orders of magnitude | Statement: [Newcomb–Benford law, typicalDatasetCondition, data spanning several orders of magnitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDatasetCondition Context triple: [Newcomb–Benford law, typicalDatasetCondition, data spanning several orders of magnitude]
-
A.
evaluationDataset
Indicates that a dataset is used as a benchmark or test set for evaluating the performance or quality of a system, model, or method.
-
B.
hasTypicalConditions
chosen
Indicates that something is associated with conditions or circumstances that are commonly or normally present for it.
-
C.
hasLongTermDatasetSince
Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in time.
-
D.
targetedCondition
Indicates that an action, intervention, or entity is specifically directed toward affecting, treating, or addressing a particular condition.
-
E.
typicalConsistency
Indicates that one entity characteristically maintains a regular or expected level of consistency in relation to another entity or context.
- 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.