Triple
T27205847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Coast Music Award |
E683860
|
entity |
| Predicate | typicalHostProvinces |
P79811
|
FINISHED |
| Object | Nova Scotia |
—
|
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: Nova Scotia | Statement: [East Coast Music Award, typicalHostProvinces, Nova Scotia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHostProvinces Context triple: [East Coast Music Award, typicalHostProvinces, Nova Scotia]
-
A.
hostProvinceOrState
Indicates that one administrative province or state serves as the host or location for another entity, such as an event, organization, or facility.
-
B.
mainProvinces
Indicates that certain provinces are the primary or most significant administrative regions associated with a given entity.
-
C.
typicalHostRegion
chosen
Indicates the geographic region where a host is most commonly or characteristically found or associated.
-
D.
baseProvince
Indicates that one administrative or territorial unit serves as the primary or originating province associated with another entity.
-
E.
adminProvince
Indicates that one entity serves as the administrative province or primary provincial jurisdiction for another entity.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: April 27, 2026, 9:38 a.m.