Triple
T38079847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia vs. Georgia Tech |
E950820
|
entity |
| Predicate | primaryMeetingFrequency |
P2557
|
FINISHED |
| Object | annual |
—
|
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: annual | Statement: [Georgia vs. Georgia Tech, primaryMeetingFrequency, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMeetingFrequency Context triple: [Georgia vs. Georgia Tech, primaryMeetingFrequency, annual]
-
A.
meetingFrequency
chosen
Indicates how often a meeting or recurring gathering takes place over a given period.
-
B.
appointmentFrequency
Indicates how often appointments are scheduled or expected to occur within a given time period.
-
C.
meetsRegularly
Indicates that two or more entities come together on a recurring or scheduled basis.
-
D.
dealFrequency
Indicates how often a particular deal, transaction, or agreement occurs within a given period.
-
E.
usualFrequency
Indicates how often an action, event, or relationship typically occurs within a given time frame.
- 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_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.