Triple
T2117821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Scottish National Orchestra |
E43847
|
entity |
| Predicate | toursInternationally |
P28884
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Royal Scottish National Orchestra, toursInternationally, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toursInternationally Context triple: [Royal Scottish National Orchestra, toursInternationally, true]
-
A.
touredIn
Indicates that an entity traveled to and visited a particular place, typically as part of a tour or series of visits.
-
B.
isFrequentlyPerformedOnTourBy
Indicates that an action or piece (such as a song, routine, or performance) is regularly and commonly carried out by an entity while they are on tour.
-
C.
operatesInternationally
chosen
Indicates that the entity conducts activities or business across national borders in multiple countries.
-
D.
touringActivity
Indicates an activity where an entity travels from place to place, typically for visiting, performing, or sightseeing purposes.
-
E.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb2f6f608190937889bb393fe7c6 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.