Triple
T3891579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Palace of Fez |
E88072
|
entity |
| Predicate | publicView |
P1079
|
FINISHED |
| Object | main gates visible from outside |
—
|
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: main gates visible from outside | Statement: [Royal Palace of Fez, publicView, main gates visible from outside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicView Context triple: [Royal Palace of Fez, publicView, main gates visible from outside]
-
A.
publicProfile
Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
-
B.
socialView
Indicates a relationship where one entity views, accesses, or inspects another entity’s social-related information, profile, or activity.
-
C.
primaryView
Indicates that one view or representation is designated as the main or default perspective among multiple possible views of the same entity or content.
-
D.
publicAccess
chosen
Indicates that something is available for use, entry, or viewing by the general public without special restrictions or permissions.
-
E.
viewedBy
Indicates that something has been seen, observed, or watched by a particular entity.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.