Triple
T14363939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Boathouse, Wylam |
E356177
|
entity |
| Predicate | isWellRegarded |
P15867
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Boathouse, Wylam, isWellRegarded, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWellRegarded Context triple: [The Boathouse, Wylam, isWellRegarded, true]
-
A.
isWidelyKnown
Indicates that something is generally recognized or familiar to a large number of people.
-
B.
isHighlyPrized
Indicates that something is regarded with exceptional value, admiration, or importance, often being especially sought after or cherished.
-
C.
hasHighRatingOn
Indicates that one entity is evaluated or reviewed on another entity’s platform or system with a rating that meets or exceeds a defined high threshold.
-
D.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
E.
respectedAs
chosen
Indicates that one entity regards another with esteem or honor, recognizing their value, status, or authority.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fad48748190a0f34ca4d02f9a3c |
completed | April 14, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:15 a.m.