Triple
T14222392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dugald Stewart Monument |
E352528
|
entity |
| Predicate | popularViewpointFor |
P113278
|
FINISHED |
| Object | views of Edinburgh |
—
|
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: views of Edinburgh | Statement: [Dugald Stewart Monument, popularViewpointFor, views of Edinburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularViewpointFor Context triple: [Dugald Stewart Monument, popularViewpointFor, views of Edinburgh]
-
A.
popularFor
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
-
B.
popularFrom
Indicates that something gains or holds popularity starting from a specific time, source, or context.
-
C.
popularVoteType
Indicates the specific method or category by which a popular vote is conducted or classified in an election or decision process.
-
D.
popularDescription
Indicates that an entity has a commonly used or widely recognized descriptive text or label associated with it.
-
E.
popularVote
Indicates the number or share of votes directly cast by the general electorate for a candidate or option in an election.
- F. None of above. chosen
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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6227c288819081473ce44f9f0934 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:06 a.m.