Triple
T38079863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia vs. Georgia Tech |
E950820
|
entity |
| Predicate | hasSeriesLeader |
P15678
|
FINISHED |
| Object | Georgia Bulldogs football |
—
|
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: Georgia Bulldogs football | Statement: [Georgia vs. Georgia Tech, hasSeriesLeader, Georgia Bulldogs football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeriesLeader Context triple: [Georgia vs. Georgia Tech, hasSeriesLeader, Georgia Bulldogs football]
-
A.
seriesLeader
chosen
Indicates that one entity serves as the primary leader, head, or main responsible figure for a particular series involving another entity.
-
B.
hasLeadInSeries
Indicates that one entity serves as the primary or starring role in a series associated with another entity.
-
C.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
D.
hasLeaderInStory
Indicates that one entity serves as the leader of another entity within the context of a specific story or narrative.
-
E.
recordedAsLeaderBy
Indicates that an entity is documented or registered as the leader by a particular source, system, or authority.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
Created at: May 3, 2026, 4:21 p.m.