Triple
T12200077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Tattoo |
E290686
|
entity |
| Predicate | tourHistory |
P71435
|
FINISHED |
| Object | has toured in Europe |
—
|
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: has toured in Europe | Statement: [Rose Tattoo, tourHistory, has toured in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourHistory Context triple: [Rose Tattoo, tourHistory, has toured in Europe]
-
A.
teamHistory
Indicates that there exists a historical relationship or record connecting a team with its past events, compositions, or performance over time.
-
B.
movementHistory
Indicates a record of how an entity has moved over time, capturing the sequence, timing, and possibly locations of its movements.
-
C.
hasTourHistory
chosen
Indicates that an entity has a record of past tours or tour-related activities.
-
D.
recordsTour
Indicates that an entity documents or logs information about a tour, such as its details, occurrences, or progress.
-
E.
formerTour
Indicates that an entity previously participated in or was associated with a particular tour, but is no longer part of it.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:50 p.m.