Triple
T1864403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Full Moon |
E34886
|
entity |
| Predicate | isAssociatedWithTour |
P26147
|
FINISHED |
| Object | Full Moon promotional performances |
—
|
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: Full Moon promotional performances | Statement: [Full Moon, isAssociatedWithTour, Full Moon promotional performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithTour Context triple: [Full Moon, isAssociatedWithTour, Full Moon promotional performances]
-
A.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
B.
tourAssociation
chosen
Indicates a relationship where an entity is linked or affiliated with a specific tour, such as organizing, sponsoring, or being formally connected to that tour.
-
C.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
touredIn
Indicates that an entity traveled to and visited a particular place, typically as part of a tour or series of visits.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.