Triple
T17091047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France women’s national basketball team |
E414725
|
entity |
| Predicate | isOlympicTeam |
P72659
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [France women’s national basketball team, isOlympicTeam, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOlympicTeam Context triple: [France women’s national basketball team, isOlympicTeam, true]
-
A.
hasOlympicCountry
Indicates that an entity is associated with or represents a specific country in the context of the Olympic Games.
-
B.
OlympicStatus
Indicates that an entity holds a particular status or role in relation to the Olympic Games (e.g., being an Olympic sport, event, athlete, or host).
-
C.
olympicTeamRelated
chosen
Indicates that there is a relationship involving an Olympic team, such as membership, representation, or official association with that team.
-
D.
hasOlympians
Indicates that an entity includes, is associated with, or contains one or more Olympian participants or members.
-
E.
OlympicTeammate
Indicates that two individuals were members of the same Olympic team at the same Olympic Games.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfa09b08190be4303dd0d174feb |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.