Triple
T6718838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Square |
E153341
|
entity |
| Predicate | containsViewOf |
P854
|
FINISHED |
| Object | Royal Palace façade |
—
|
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: Royal Palace façade | Statement: [Crown Square, containsViewOf, Royal Palace façade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsViewOf Context triple: [Crown Square, containsViewOf, Royal Palace façade]
-
A.
hasView
chosen
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
B.
hasViewThrough
Indicates that one entity can be seen or visually perceived through another entity acting as an intermediate medium or opening.
-
C.
viewHeldBy
Indicates that a particular view, perspective, or opinion is possessed, maintained, or endorsed by a specific entity.
-
D.
supportsView
Indicates that one entity provides the capability to display, render, or present another entity in a particular view or format.
-
E.
viewOfSon
Indicates a relationship where one entity holds a particular perspective, opinion, or way of seeing another entity referred to as the son.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d135d27c819088c45839ad0e7bab |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:07 p.m.