Triple
T38039464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maritimes Division |
E949439
|
entity |
| Predicate | teamsLocatedIn |
P3777
|
FINISHED |
| Object | Maritime provinces |
—
|
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: Maritime provinces | Statement: [Maritimes Division, teamsLocatedIn, Maritime provinces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamsLocatedIn Context triple: [Maritimes Division, teamsLocatedIn, Maritime provinces]
-
A.
teamLocationExample
Indicates that a specific location is provided as an example of where a team is based or operates.
-
B.
teamLocation
chosen
Indicates that a team is based in, associated with, or operates from a particular geographic location.
-
C.
teamLocationCriterion
Indicates a condition that specifies or restricts where a team must be located.
-
D.
draftTeamLocation
Indicates the location associated with a team's draft, such as the city or venue where the drafting event or selection took place.
-
E.
collegeTeamLocation
Indicates the geographic location (such as city, state, or region) associated with a particular college sports 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:20 p.m.