Triple
T10487979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Dining Room (Royal Yacht Britannia) |
E247339
|
entity |
| Predicate | locatedOnDeck |
P74241
|
FINISHED |
| Object | main deck of Royal Yacht Britannia |
—
|
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 deck of Royal Yacht Britannia | Statement: [State Dining Room (Royal Yacht Britannia), locatedOnDeck, main deck of Royal Yacht Britannia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnDeck Context triple: [State Dining Room (Royal Yacht Britannia), locatedOnDeck, main deck of Royal Yacht Britannia]
-
A.
locatedOnLevel
chosen
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
-
B.
seatLocatedIn
Indicates that a seat is situated within or belongs to a specific location or area.
-
C.
seatLocatedAt
Indicates that a seat is positioned or situated at a specific location or place.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
seatOftenLocatedIn
Indicates that one type of seat is commonly or typically found within a particular location or setting.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5096b609c81909e23fd8fb6426f4a |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.