Triple
T33779973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Loons |
E865625
|
entity |
| Predicate | supportsClubIn |
P24484
|
FINISHED |
| Object | Major League Soccer |
E982
|
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: Major League Soccer | Statement: [Red Loons, supportsClubIn, Major League Soccer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsClubIn Context triple: [Red Loons, supportsClubIn, Major League Soccer]
-
A.
supportedClub
Indicates that one entity has given their backing, endorsement, or assistance to a particular club.
-
B.
supportsClubInLeague
chosen
Indicates that one entity provides backing or sponsorship for a club participating in a particular league.
-
C.
supportsClubIdentity
Indicates that one entity actively upholds, reinforces, or contributes to maintaining the identity, values, or character of a club.
-
D.
supportedClubLeague
Indicates that an entity (typically a person or group) actively supported a particular sports club participating in a specified league.
-
E.
supportsClubConference
Indicates that one entity provides assistance, resources, or endorsement to help a club organize, host, or participate in a conference.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
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_6a366587d078819097947525526dce13 |
completed | June 20, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:45 a.m.