Triple
T26398383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Soccer League |
E663634
|
entity |
| Predicate | featuredClubs |
P50991
|
FINISHED |
| Object | Sydney City |
—
|
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: Sydney City | Statement: [National Soccer League, featuredClubs, Sydney City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredClubs Context triple: [National Soccer League, featuredClubs, Sydney City]
-
A.
featuresClubs
chosen
Indicates that something includes or presents one or more clubs as part of its composition, content, or offering.
-
B.
topClubsParticipateIn
Indicates that leading or highest-ranked clubs take part in a specified event, competition, or activity.
-
C.
otherProminentClub
Indicates a relationship where an entity is associated with another club that is also notable or high-profile, distinct from its primary or main club.
-
D.
featuresClubSuccess
Indicates that something highlights or showcases the success or achievements of a club.
-
E.
notableClub
Indicates that an entity is prominently associated with or recognized for membership in a particular club or organization.
- 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_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 26, 2026, 11:30 p.m.