Triple
T6438498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Runner |
E129958
|
entity |
| Predicate | scoresWhen |
P70624
|
FINISHED |
| Object | he legally touches home plate before the third out |
—
|
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: he legally touches home plate before the third out | Statement: [The Runner, scoresWhen, he legally touches home plate before the third out]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoresWhen Context triple: [The Runner, scoresWhen, he legally touches home plate before the third out]
-
A.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
B.
scoreUsedFor
Indicates that a particular score or rating is used for a specific purpose, decision, or downstream process.
-
C.
scoredFor
Indicates that one entity achieved points or a score on behalf of another entity, such as a player scoring for a team.
-
D.
scoreScale
Indicates the scale or range on which a score or rating is expressed or measured.
-
E.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
- F. None of above. chosen
Provenance (4 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06965a5d48190a5860da9e22dc6e0 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:45 p.m.