Triple
T27158712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Will You Be There |
E682595
|
entity |
| Predicate | labelSingleReleaseTerritory |
P67545
|
FINISHED |
| Object | Europe |
—
|
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: Europe | Statement: [Will You Be There, labelSingleReleaseTerritory, Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelSingleReleaseTerritory Context triple: [Will You Be There, labelSingleReleaseTerritory, Europe]
-
A.
releasedAsSingleInTerritory
chosen
Indicates that a work (such as a song or recording) was issued as a single in a specific geographic territory or market.
-
B.
associatedTitleTerritory
Indicates a relationship where a specific title is linked or connected to a particular territory or domain.
-
C.
publishedInTerritory
Indicates that something (such as a work, product, or edition) has been published within a specific geographic or legal territory.
-
D.
countryOfRelease
Indicates the country in which an item (such as a product, work, or media) was officially released.
-
E.
recognizedTerritory
Indicates that one entity formally acknowledges another entity’s claim of authority or ownership over a specific geographic area.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62509315481909835aa77ae8b81c2 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:17 a.m.