Triple
T6196169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oslo Cathedral |
E138512
|
entity |
| Predicate | hasRoyalPews |
P69597
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Oslo Cathedral, hasRoyalPews, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalPews Context triple: [Oslo Cathedral, hasRoyalPews, yes]
-
A.
hasSacristy
Indicates that a religious building includes or is associated with a sacristy (a room where sacred vessels, vestments, and liturgical items are kept and prepared).
-
B.
containsSeatOfMonarchy
Indicates that a place or region includes within its boundaries the official seat or residence of a monarchy’s ruling authority.
-
C.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
D.
hasChoirStalls
Indicates that a location or structure contains or is equipped with choir stalls used for seating members of a choir.
-
E.
hasPulpit
Indicates that one entity possesses, contains, or is equipped with a pulpit used for speaking or preaching.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0624571508190bd273b4a051fbe41 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:20 p.m.