Triple
T31123409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas–New York sports rivalry |
E793281
|
entity |
| Predicate | involvesTeamFromTexas |
P42264
|
FINISHED |
| Object | Dallas Cowboys |
—
|
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: Dallas Cowboys | Statement: [Texas–New York sports rivalry, involvesTeamFromTexas, Dallas Cowboys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesTeamFromTexas Context triple: [Texas–New York sports rivalry, involvesTeamFromTexas, Dallas Cowboys]
-
A.
strengthTexian
Indicates that one entity possesses or exhibits physical or metaphorical strength in relation to Texian (Texas-related) contexts or standards.
-
B.
HoustonCoach
Indicates that an individual serves as a coach for a sports team or organization based in Houston.
-
C.
hasTeamInState
Indicates that an organization or entity has at least one team located or operating within a specified state.
-
D.
associatedTeamName
chosen
Indicates the name of the team that is linked or connected to a given entity.
-
E.
stateTeam
Indicates that a team is officially associated with, represents, or belongs to a particular state.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 29, 2026, 9:05 p.m.