Triple
T725464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USL Championship |
E14715
|
entity |
| Predicate | typicalConferenceNames |
P3307
|
FINISHED |
| Object | Eastern Conference |
—
|
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: Eastern Conference | Statement: [USL Championship, typicalConferenceNames, Eastern Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalConferenceNames Context triple: [USL Championship, typicalConferenceNames, Eastern Conference]
-
A.
conferenceTitles
Indicates a relationship where one entity (such as a conference event or series) is associated with the titles under which it is or has been held.
-
B.
notableConference
Indicates that there is a significant or distinguished conference associated with the subject entity.
-
C.
conferenceType
Indicates the specific category or kind of conference associated with an entity (e.g., workshop, symposium, seminar).
-
D.
conference2
Indicates that one entity is a conference or event that is associated with, hosted by, or otherwise related to another entity.
-
E.
conference1
chosen
Indicates a relationship where an entity is associated with, participates in, or is characterized as a specific conference event or instance.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5a7fb7c819096db848fe2ba246a |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f700cc81908c6de3eedf68433c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.