Triple
T34315034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Last Farewell |
E880553
|
entity |
| Predicate | hasNotablePopularityIn |
P152493
|
FINISHED |
| Object | United States |
E14
|
NE 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: United States | Statement: [The Last Farewell, hasNotablePopularityIn, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePopularityIn Context triple: [The Last Farewell, hasNotablePopularityIn, United States]
-
A.
achievedPopularityIn
chosen
Indicates that an entity became popular or widely recognized within a specified place, group, or context.
-
B.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
-
C.
achievedPopularityVia
Indicates that an entity gained recognition or widespread acceptance through a particular method, channel, or means.
-
D.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
E.
hasNotablePopulation
Indicates that an entity is recognized for having a significant or noteworthy number of inhabitants or members.
- F. None of above.
Provenance (4 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a030d3db2748190b32fcf7b21bd0d0a |
completed | May 12, 2026, 11:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36f9b3ee148190881bc9e254043b39 |
completed | June 20, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_6a030ca6bf388190b2f6931376323da3 |
completed | May 12, 2026, 11:19 a.m. |
Created at: May 1, 2026, 1:57 a.m.