Triple
T1357840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National League Championship Series |
E29028
|
entity |
| Predicate | usesHomeFieldAdvantageRule |
P11326
|
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: [National League Championship Series, usesHomeFieldAdvantageRule, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHomeFieldAdvantageRule Context triple: [National League Championship Series, usesHomeFieldAdvantageRule, yes]
-
A.
homeFieldAdvantage
chosen
Indicates that one participant benefits from playing or operating in a familiar or home environment, gaining an advantage over the opponent.
-
B.
homeFieldAdvantageBasedOn
Indicates that the degree of home-field advantage is determined or influenced by the specified factor or condition.
-
C.
homeFieldLocation
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
-
D.
hasAdvantage
Indicates that one entity possesses a benefit, edge, or favorable position over another in a given context.
-
E.
homeFieldSurface
Indicates the type of playing surface used at a team's home field or stadium.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c28f5b988190b0be4504eabb919d |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.