Triple
T4493379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand Symphony Orchestra |
E100632
|
entity |
| Predicate | toursTo |
P31993
|
FINISHED |
| Object | international venues |
—
|
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: international venues | Statement: [New Zealand Symphony Orchestra, toursTo, international venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toursTo Context triple: [New Zealand Symphony Orchestra, toursTo, international venues]
-
A.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
-
B.
touristGatewayTo
Indicates a relationship where one place serves as the primary access point or entry hub for tourists visiting another place.
-
C.
touredIn
chosen
Indicates that an entity traveled to and visited a particular place, typically as part of a tour or series of visits.
-
D.
tourCategory
Indicates the classification or type of a tour (e.g., by theme, style, or purpose) that the tour belongs to.
-
E.
tourStopOf
Indicates that one entity is a stop or scheduled visit location within the itinerary or route of another entity’s tour.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5570ba0881908f5fb4f8d0730e64 |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.