Triple
T20438674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Jets |
E501323
|
entity |
| Predicate | teamNameUsedFor |
P7598
|
FINISHED |
| Object | women's athletic teams of South Georgia Technical College |
—
|
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: women's athletic teams of South Georgia Technical College | Statement: [Lady Jets, teamNameUsedFor, women's athletic teams of South Georgia Technical College]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamNameUsedFor Context triple: [Lady Jets, teamNameUsedFor, women's athletic teams of South Georgia Technical College]
-
A.
teamName
chosen
Indicates the relationship that assigns or associates a specific name with a particular team.
-
B.
teamNameUsedSince
Indicates the point in time since which a particular team name has been in use.
-
C.
teamNameRefersTo
Indicates that a given team name designates or refers to a specific team entity.
-
D.
teamNameType
Indicates the type or category associated with a team's name (e.g., formal name, short name, nickname).
-
E.
namedForTeam
Indicates that one entity has been given its name in honor of, or derived from, a particular team.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f112e48190a3af818c0f6ee839 |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:31 a.m.