Triple
T6443650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Conference Semifinals |
E138285
|
entity |
| Predicate | homeAndAwayStructure |
P8330
|
FINISHED |
| Object | alternating home courts |
—
|
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: alternating home courts | Statement: [Eastern Conference Semifinals, homeAndAwayStructure, alternating home courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeAndAwayStructure Context triple: [Eastern Conference Semifinals, homeAndAwayStructure, alternating home courts]
-
A.
homeAndAwayFormat
chosen
Indicates that a competition or matchup is structured so that each pair of opponents plays twice, once at each participant’s home venue and once away.
-
B.
houseOrFamily
Indicates that two entities are related through a shared house, household, or family membership.
-
C.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
D.
house1
Indicates that something is identified or classified as a house or dwelling.
-
E.
house2
Indicates a relationship where one entity is a secondary, related, or alternative house associated with another entity.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698b030481908b7bb4e16a8b3339 |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.