Triple
T26398471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-League Youth |
E663636
|
entity |
| Predicate | participatingClubType |
P19215
|
FINISHED |
| Object | A-League Men clubs |
—
|
NE NERFINISHED |
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: A-League Men clubs | Statement: [A-League Youth, participatingClubType, A-League Men clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatingClubType Context triple: [A-League Youth, participatingClubType, A-League Men clubs]
-
A.
participatingClubsFrom
Indicates that certain clubs are taking part in or are involved in an event, activity, or context originating from a specified source or organizer.
-
B.
refersToClubType
chosen
Indicates that one entity is associated with or designates a particular type or category of club.
-
C.
associatedClubSport
Indicates that there is a relationship between a club and the sport with which it is connected or aligned.
-
D.
clubTypeInvolved
Indicates that a specific type or category of club is involved or participates in the referenced event, activity, or relationship.
-
E.
memberClubsType
Indicates that an entity is associated as a member with clubs of 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 11:30 p.m.