Triple
T19617684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doosan Arena |
E470909
|
entity |
| Predicate | hasRegulationPitch |
P38697
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Doosan Arena, hasRegulationPitch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegulationPitch Context triple: [Doosan Arena, hasRegulationPitch, yes]
-
A.
regulationPitch
Indicates that an entity controls, adjusts, or maintains the pitch (e.g., frequency or perceived highness/lowness) of another entity or signal.
-
B.
hasPitchType
chosen
Indicates that an entity is associated with, or characterized by, a specific type or category of pitch.
-
C.
hasRegulations
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
D.
usesDesignatedHitterRule
Indicates that a baseball league, team, or game employs the designated hitter rule, allowing a player to bat in place of the pitcher.
-
E.
usesLimitedOversRules
Indicates that the action or event is conducted under limited-overs rules, typically involving a fixed maximum number of overs per side.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e346548190b12e38d716bdfc4f |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.