Triple
T31438932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shhwonk Fortress |
E802014
|
entity |
| Predicate | hasPerspectiveInWork |
P8789
|
FINISHED |
| Object | 2.5D |
—
|
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: 2.5D | Statement: [Shhwonk Fortress, hasPerspectiveInWork, 2.5D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerspectiveInWork Context triple: [Shhwonk Fortress, hasPerspectiveInWork, 2.5D]
-
A.
workPerspective
Indicates a relationship where one entity expresses or embodies a particular viewpoint, approach, or interpretive angle on work or working.
-
B.
perspectiveOf
chosen
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
-
C.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
-
D.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
E.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 30, 2026, 9:04 p.m.