Triple
T26390825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dowdall system |
E663406
|
entity |
| Predicate | scoreAggregation |
P120548
|
FINISHED |
| Object | sum of weighted preference scores |
—
|
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: sum of weighted preference scores | Statement: [Dowdall system, scoreAggregation, sum of weighted preference scores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreAggregation Context triple: [Dowdall system, scoreAggregation, sum of weighted preference scores]
-
A.
recordAggregateScore
chosen
Indicates recording a combined or total score derived from multiple individual scores or components.
-
B.
scoreAssignment
Indicates evaluating and assigning a grade or numerical score to an assignment.
-
C.
scoresWhen
Indicates that one entity achieves a score or points at the time or under the condition specified by another entity or event.
-
D.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
E.
scoreUsedFor
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610bf1e248190a186aed862513478 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:25 p.m.