Triple
T27426697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Bonhomme |
E690505
|
entity |
| Predicate | hasFlownDisplayTeams |
P2085
|
FINISHED |
| Object | The Matadors |
—
|
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: The Matadors | Statement: [Paul Bonhomme, hasFlownDisplayTeams, The Matadors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlownDisplayTeams Context triple: [Paul Bonhomme, hasFlownDisplayTeams, The Matadors]
-
A.
hasAerobaticDisplayTeam
chosen
Indicates that an entity maintains or is associated with a team that performs aerobatic flying displays.
-
B.
previousTeamNamesAlsoAssociatedWithFranchise
Indicates that the earlier team names are also historically or officially linked to the same franchise.
-
C.
hasFormerTeam
Indicates that an entity was previously a member of, played for, or was affiliated with a team in the past but is no longer associated with that team.
-
D.
usesTeamFranchises
Indicates that an entity makes use of, operates through, or is associated with one or more team-based franchise organizations.
-
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_69ef52003fb48190b0f1295246182a86 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 12:41 p.m.