Triple
T9880756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nova Nation |
E180796
|
entity |
| Predicate | homeGameRole |
P91576
|
FINISHED |
| Object | create home-court advantage |
—
|
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: create home-court advantage | Statement: [Nova Nation, homeGameRole, create home-court advantage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGameRole Context triple: [Nova Nation, homeGameRole, create home-court advantage]
-
A.
homeGroundRole
Indicates that an entity serves in the role of home ground or primary venue for another entity (such as a team or organization).
-
B.
homeGamesOf
Indicates that the subject is a home game (or set of home games) played by the specified team or entity.
-
C.
playRoleIn
Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
-
D.
homeGamesState
Indicates the state or location context in which a team's home games are played.
-
E.
gamingSpace
Indicates a relationship where a space, area, or environment is designated or used specifically for gaming activities.
- F. None of above. chosen
Provenance (4 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb41639c88190a9ef3d950485e3ab |
completed | April 2, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:38 p.m.