Triple
T4967492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Texas Mean Green |
E111561
|
entity |
| Predicate | foundedForFootball |
P935
|
FINISHED |
| Object | 1913 |
—
|
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: 1913 | Statement: [North Texas Mean Green, foundedForFootball, 1913]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedForFootball Context triple: [North Texas Mean Green, foundedForFootball, 1913]
-
A.
foundedAsTopLevelClub
Indicates that an organization was originally established directly as a top-tier club, rather than being promoted or restructured from a lower level.
-
B.
foundedAsRepresentativeTeam
Indicates that an entity was established specifically to serve as a representative team for a larger group, organization, or region.
-
C.
foundedFor
chosen
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
D.
associatedClubFounded
Indicates that there exists a club associated with an entity and specifies the date or time at which that associated club was founded.
-
E.
sportTeamFounded
Indicates the event or point in time when a sports team was established or created.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.