Triple
T11763760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson Generals |
E279724
|
entity |
| Predicate | hasTeamNameOrigin |
P30598
|
FINISHED |
| Object | named after local military heritage |
—
|
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: named after local military heritage | Statement: [Jackson Generals, hasTeamNameOrigin, named after local military heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamNameOrigin Context triple: [Jackson Generals, hasTeamNameOrigin, named after local military heritage]
-
A.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
usedAsTeamNameUntil
Indicates that an entity served as a team's name up to, but not beyond, a specified point in time.
-
C.
teamOrigin
Indicates the place, organization, or context from which a team originates or is formed.
-
D.
foundedAsTeam
Indicates that an organization or club was originally established in the form of a team.
-
E.
teamNameInspiredBy
chosen
Indicates that the name of one team was chosen based on, influenced by, or derived from another entity (such as a person, place, concept, or other 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5248e0881909ed1b4df7be422f7 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.