Triple
T1131666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Mary's Gaels men's basketball |
E23043
|
entity |
| Predicate | homeCourtAdvantageReputation |
P11326
|
FINISHED |
| Object | strong |
—
|
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: strong | Statement: [Saint Mary's Gaels men's basketball, homeCourtAdvantageReputation, strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCourtAdvantageReputation Context triple: [Saint Mary's Gaels men's basketball, homeCourtAdvantageReputation, strong]
-
A.
homeScore
Indicates the number of points or goals scored by the home team or home participant in a game or match.
-
B.
homeIceAdvantageBasedOn
Indicates that the degree of home-ice advantage is determined or influenced by the specified factor or condition.
-
C.
homeFieldAdvantage
chosen
Indicates that one participant benefits from playing or operating in a familiar or home environment, gaining an advantage over the opponent.
-
D.
homeFieldAdvantageBasedOn
Indicates that the degree of home-field advantage is determined or influenced by the specified factor or condition.
-
E.
homeFieldLocation
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.