Triple
T19689469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | distance covariance |
E472795
|
entity |
| Predicate | isEstimatedBy |
P70307
|
FINISHED |
| Object | sample distance covariance |
—
|
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: sample distance covariance | Statement: [distance covariance, isEstimatedBy, sample distance covariance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEstimatedBy Context triple: [distance covariance, isEstimatedBy, sample distance covariance]
-
A.
areEstimatedIn
Indicates that a value or quantity is approximated or inferred within a specified context, framework, or unit.
-
B.
wasFirstEstimatedBy
Indicates that an initial estimation or calculation of something was made by a particular agent or source.
-
C.
estimatedUsing
chosen
Indicates that one entity’s value, state, or outcome is derived by applying an estimation method, model, or procedure based on another entity.
-
D.
approximateEstimation
Indicates an estimation relationship where one value or assessment is only roughly or closely, but not exactly, equal to another.
-
E.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420f1a0c8190ae59aa0ab3ff2802 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.