Triple
T2750185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Britain |
E60964
|
entity |
| Predicate | teamNameUsedSince |
P41628
|
FINISHED |
| Object | early modern Olympic era |
—
|
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: early modern Olympic era | Statement: [Great Britain, teamNameUsedSince, early modern Olympic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamNameUsedSince Context triple: [Great Britain, teamNameUsedSince, early modern Olympic era]
-
A.
teamName
Indicates the relationship that assigns or associates a specific name with a particular team.
-
B.
team1LaterKnownAs
Indicates that the first team was later renamed to or became known by the identity of the second team.
-
C.
team1FoundedAsCurrentName
Indicates that the first team entity was originally founded under its current name, rather than having changed names since its founding.
-
D.
yearsWithTeam
Indicates the number of years an entity (typically a person) has been associated with or part of a particular team.
-
E.
previousTeamNamesAlsoAssociatedWithFranchise
Indicates that the earlier team names are also historically or officially linked to the same franchise.
- F. None of above. chosen
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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb52b1d48190b6ab511cc8834a14 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd91497ec8190927e91ad33549eda |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:56 p.m.