Triple
T19498086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 義大犀牛 |
E487825
|
entity |
| Predicate | 球隊主場優勢市場 |
P11326
|
FINISHED |
| Object | 高雄市及周邊縣市 |
—
|
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: 高雄市及周邊縣市 | Statement: [義大犀牛, 球隊主場優勢市場, 高雄市及周邊縣市]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 球隊主場優勢市場 Context triple: [義大犀牛, 球隊主場優勢市場, 高雄市及周邊縣市]
-
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.
homeFieldAdvantageFor
Indicates that one entity benefits from playing or operating in its own familiar location or environment when facing the other entity.
-
D.
leagueWithHomeFieldAdvantageAwarded
Indicates that in this league context, a home-field advantage has been granted or assigned, typically for a particular team, game, or playoff series.
-
E.
homeFieldForALTeam
Indicates that a particular stadium or ballpark serves as the designated home field for a specific American League baseball team.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63493232881909fc33fb84da3e1b5 |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.