Triple
T30093429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acadia Axewomen track and field |
E764796
|
entity |
| Predicate | associatedMen’sTeam |
P42591
|
FINISHED |
| Object | Acadia Axemen track and field |
E194310
|
NE 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: Acadia Axemen track and field | Statement: [Acadia Axewomen track and field, associatedMen’sTeam, Acadia Axemen track and field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMen’sTeam Context triple: [Acadia Axewomen track and field, associatedMen’sTeam, Acadia Axemen track and field]
-
A.
hasMenTeam
chosen
Indicates that an entity possesses, is associated with, or fields a men’s team.
-
B.
refersToMenTeam
Indicates that something is associated with, designates, or pertains specifically to a men's team.
-
C.
hasMen'sTeamsName
Indicates that an entity has a specific name used for its men's sports team or teams.
-
D.
menTeamPlaysIn
Indicates that a men's team participates or competes in a particular league, division, or competition.
-
E.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
- F. None of above.
Provenance (4 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a274328b9e081908719e29052bf2685 |
completed | June 8, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:06 p.m.