Triple
T6438485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Runner |
E129958
|
entity |
| Predicate | canAdvanceOn |
P16805
|
FINISHED |
| Object | batted ball |
—
|
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: batted ball | Statement: [The Runner, canAdvanceOn, batted ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAdvanceOn Context triple: [The Runner, canAdvanceOn, batted ball]
-
A.
mayAdvanceTo
chosen
Indicates that one entity is permitted or eligible to progress, move, or be promoted to another specified state, level, or position.
-
B.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
C.
canPass
Indicates that one entity is able or permitted to move through, cross, or successfully traverse another entity or barrier.
-
D.
canConcurIn
Indicates that one entity is able or permitted to agree with, coincide with, or participate jointly in the same event, decision, or condition as another entity.
-
E.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
- 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_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. |
Created at: March 22, 2026, 4:45 p.m.