Triple
T33671245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmonton Oilers prospects |
E862623
|
entity |
| Predicate | primaryFarmTeam |
P159674
|
FINISHED |
| Object | Bakersfield Condors |
E245812
|
NE 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: Bakersfield Condors | Statement: [Edmonton Oilers prospects, primaryFarmTeam, Bakersfield Condors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFarmTeam Context triple: [Edmonton Oilers prospects, primaryFarmTeam, Bakersfield Condors]
-
A.
hasFarmTeam
Indicates that one organization serves as a lower-level or affiliated team that develops players or resources for another organization.
-
B.
primaryTeam
Indicates that one entity is the main or principal team associated with another entity, such as a person, project, or organization.
-
C.
farmTeamOf
chosen
Indicates that one sports team serves as a developmental or minor-league affiliate for another, higher-level team.
-
D.
primaryTeams
Indicates that one or more teams are the main or principal teams associated with a given entity.
-
E.
primaryTeamBrand
Indicates the brand or franchise that serves as an entity’s main or primary team affiliation.
- F. None of above.
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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36822364208190adb4e9ce6a3524b0 |
completed | June 20, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:42 a.m.