Triple
T27713398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Oslo, Akershus and Tønsberg |
E698751
|
entity |
| Predicate | seatOrStronghold |
P46785
|
FINISHED |
| Object | Tønsberg Fortress |
—
|
NE NERFINISHED |
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: Tønsberg Fortress | Statement: [Duke of Oslo, Akershus and Tønsberg, seatOrStronghold, Tønsberg Fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatOrStronghold Context triple: [Duke of Oslo, Akershus and Tønsberg, seatOrStronghold, Tønsberg Fortress]
-
A.
seatLocatedIn
Indicates that a seat is situated within or belongs to a specific location or area.
-
B.
seatLocatedAt
Indicates that a seat is positioned or situated at a specific location or place.
-
C.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
-
D.
seatOrBase
Indicates that one entity serves as the seat, base, or supporting foundation for another entity.
-
E.
strongholdOf
chosen
Indicates that a location serves as a primary fortified base, center of power, or main stronghold for 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 3:03 p.m.