Triple
T28405927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier Lacrosse League |
E719526
|
entity |
| Predicate | hasTeamAffiliation |
P164958
|
FINISHED |
| Object | not city-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: not city-based | Statement: [Premier Lacrosse League, hasTeamAffiliation, not city-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamAffiliation Context triple: [Premier Lacrosse League, hasTeamAffiliation, not city-based]
-
A.
hasFatherTeamAssociation
Indicates a relationship where an entity is associated with a team through or by virtue of its father’s team affiliation.
-
B.
playerAffiliation
Indicates the organization, team, or group with which a player is formally associated or aligned.
-
C.
hasMLBTeamID
Indicates that an entity is associated with a specific Major League Baseball (MLB) team identifier.
-
D.
teamAffiliations
chosen
Indicates that one entity is or has been a member of, associated with, or officially aligned to a particular team.
-
E.
hasCountyTeamAffiliation
Indicates that an entity is affiliated with, represents, or is associated with a specific county-level team.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 28, 2026, 1:23 a.m.