Triple
T35562304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Conference (NBA G League) |
E1027667
|
entity |
| Predicate | teamLimitType |
P183407
|
FINISHED |
| Object | franchise-based |
—
|
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: franchise-based | Statement: [Western Conference (NBA G League), teamLimitType, franchise-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamLimitType Context triple: [Western Conference (NBA G League), teamLimitType, franchise-based]
-
A.
teamLimitPerGame
Indicates the maximum number of times a team is allowed to participate or be involved in a single game or match.
-
B.
teamLimitPerAssociation
Indicates the maximum number of teams that can be associated with a single association or grouping.
-
C.
teamRosterLimit
Indicates the maximum number of members that are allowed to be on a team’s roster.
-
D.
teamLimitInRecentEditions
Indicates a constraint on the number of teams allowed to participate in the most recent editions of a competition or event.
-
E.
teamConstraint
Indicates a rule or limitation governing how entities can be grouped, associated, or operate together as a team.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.