Triple
T659147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA G League |
E11714
|
entity |
| Predicate | hasPlayerContractType |
P405
|
FINISHED |
| Object | two-way contracts with NBA teams |
—
|
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: two-way contracts with NBA teams | Statement: [NBA G League, hasPlayerContractType, two-way contracts with NBA teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayerContractType Context triple: [NBA G League, hasPlayerContractType, two-way contracts with NBA teams]
-
A.
typeOfContract
chosen
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
B.
hasPartnershipType
Indicates the specific kind or category of partnership relationship that exists between entities.
-
C.
hasOperatorContractStart
Indicates the date on which an operator’s contractual agreement with another entity begins.
-
D.
hasContactType
Indicates the specific kind or category of contact relationship that exists between two entities.
-
E.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d1406ec8190abf546549264c85d |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.