Triple
T18335617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bikini Olympia |
E439262
|
entity |
| Predicate | introducedAsDivision |
P131411
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [Bikini Olympia, introducedAsDivision, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsDivision Context triple: [Bikini Olympia, introducedAsDivision, 2010s]
-
A.
introducedDivisions
Indicates that one entity caused new divisions, separations, or groupings to be created within another entity or context.
-
B.
hasFormerDivision
Indicates that an entity previously had another entity as one of its internal divisions or sub-units, but no longer does.
-
C.
formerDivisionLevel
Indicates that an entity previously held a certain division level or tier but no longer does so.
-
D.
usedDivision
Indicates that one entity employed or applied a particular division (such as a subgroup, department, or partition) in performing an action or fulfilling a function.
-
E.
isPartOfDivision
Indicates that one entity belongs to, or is contained within, a specific division of a larger organizational or structural unit.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecd759481909703ed2d0d68199f |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e4561d665081908ec555344e76d82b |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 10:37 a.m.