Triple
T30079868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Britney: Piece of Me |
E764421
|
entity |
| Predicate | hasTourVersion |
P181152
|
FINISHED |
| Object | Britney: Piece of Me Tour |
—
|
NE NERFINISHED |
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: Britney: Piece of Me Tour | Statement: [Britney: Piece of Me, hasTourVersion, Britney: Piece of Me Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourVersion Context triple: [Britney: Piece of Me, hasTourVersion, Britney: Piece of Me Tour]
-
A.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
B.
hasTourAccess
Indicates that an entity is permitted to enter or participate in a specified tour.
-
C.
hasTourElement
Indicates that something includes or is associated with a specific element or component of a tour.
-
D.
hasTouringConfiguration
Indicates that an entity is associated with a specific setup or arrangement used for touring activities.
-
E.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 29, 2026, 7:02 p.m.