Triple
T28943750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O1 |
E730523
|
entity |
| Predicate | runNumber |
P86404
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [O1, runNumber, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runNumber Context triple: [O1, runNumber, 1]
-
A.
runsTotal
chosen
Indicates the total number of runs accumulated or recorded for an entity over a specified period or context.
-
B.
runsFor
Indicates that an entity performs a running activity on behalf of, or as a representative of, another entity (such as a team, organization, or cause).
-
C.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
D.
runsPer
Indicates a relationship where one entity performs running actions at a specified rate or frequency relative to another measure (such as time, distance, or event).
-
E.
trialNumber
Indicates the ordinal position or sequence index of a specific trial within a series of trials.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65b85839c8190be57052eaef1d74f |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:38 a.m.