Triple
T18704894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StatisticsGen |
E457343
|
entity |
| Predicate | canCompute |
P31625
|
FINISHED |
| Object | feature means |
—
|
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: feature means | Statement: [StatisticsGen, canCompute, feature means]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCompute Context triple: [StatisticsGen, canCompute, feature means]
-
A.
usesComputationMethod
Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
-
B.
isUsedToCompute
Indicates that one entity serves as an input, basis, or resource for performing a calculation or deriving a result about another entity.
-
C.
canDetermine
chosen
Indicates that one entity has the ability or authority to find out, establish, or decide the state, value, or outcome of another entity or situation.
-
D.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
computationInput
Indicates that an entity serves as input data or parameters consumed by a computation or processing activity.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671665bc8190b9b4a4ce4ec5b2eb |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.