Triple
T29294669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overture to Candide |
E742788
|
entity |
| Predicate | popularAs |
P104046
|
FINISHED |
| Object | concert opener |
—
|
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: concert opener | Statement: [Overture to Candide, popularAs, concert opener]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularAs Context triple: [Overture to Candide, popularAs, concert opener]
-
A.
popularFrom
Indicates that something gains or holds popularity starting from a specific time, source, or context.
-
B.
popularFor
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
-
C.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
D.
popular
Indicates that an entity is widely liked, admired, or favored by many people compared to alternatives.
-
E.
isPopularAs
chosen
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 28, 2026, 1:05 p.m.