Triple
T27034513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ジョージタウン大学 |
E681015
|
entity |
| Predicate | 所属スポーツカンファレンス |
P130997
|
FINISHED |
| Object | ビッグ・イースト・カンファレンス |
—
|
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: ビッグ・イースト・カンファレンス | Statement: [ジョージタウン大学, 所属スポーツカンファレンス, ビッグ・イースト・カンファレンス]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 所属スポーツカンファレンス Context triple: [ジョージタウン大学, 所属スポーツカンファレンス, ビッグ・イースト・カンファレンス]
-
A.
formerAthleticConference
Indicates that an entity previously belonged to a particular athletic conference but is no longer a member.
-
B.
athleticConferenceContext
chosen
Indicates the relationship between an entity and the athletic conference setting or framework within which it participates or is relevant.
-
C.
isMultiSportConference
Indicates that a sports conference encompasses multiple sports rather than being dedicated to a single sport.
-
D.
leagueConference
Indicates that a sports league is associated with, organized into, or belongs to a particular conference within its competitive structure.
-
E.
isNonFootballConference
Indicates that an entity (such as a school or team) belongs to a conference that does not participate in football competition.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62266b8b48190a050b4953753e5a7 |
completed | May 2, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:15 a.m.