Triple
T28471708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Soccer Association |
E720455
|
entity |
| Predicate | importedClubsFrom |
P86409
|
FINISHED |
| Object | England |
—
|
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: England | Statement: [United Soccer Association, importedClubsFrom, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importedClubsFrom Context triple: [United Soccer Association, importedClubsFrom, England]
-
A.
formerlyIncludedClubsFrom
chosen
Indicates that the subject entity previously included, as part of its organization or membership, the clubs originating from the object entity.
-
B.
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.
-
C.
refersToClubFrom
Indicates that one entity is referencing or pointing to a specific club as its related or associated club.
-
D.
associatedClubOrigin
Indicates that there is a relationship between an entity and the place or source from which its associated club originates.
-
E.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 2:49 a.m.