Triple
T37524363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Galactica |
E932869
|
entity |
| Predicate | runLengthDescription |
P188203
|
FINISHED |
| Object | very short run |
—
|
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: very short run | Statement: [Via Galactica, runLengthDescription, very short run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runLengthDescription Context triple: [Via Galactica, runLengthDescription, very short run]
-
A.
hasInrunLength
Indicates the length of the inrun portion (approach or run-up) associated with an activity, structure, or course.
-
B.
repeatUnitLength
Indicates the length or size of a unit that is repeated within a larger pattern, sequence, or structure.
-
C.
mostRuns
Indicates that one entity has scored a greater number of runs than all comparable entities in a given context or set.
-
D.
repetitionCount
Indicates the number of times a particular event, action, or pattern is repeated within a given context.
-
E.
inningLength
Indicates the duration or number of units (e.g., outs, minutes, or pitches) that make up a single inning in a game or sporting event.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.