Triple
T543154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oheka Castle |
E12674
|
entity |
| Predicate | inspirationFor |
P4910
|
FINISHED |
| Object | fictional estates in popular culture |
—
|
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: fictional estates in popular culture | Statement: [Oheka Castle, inspirationFor, fictional estates in popular culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspirationFor Context triple: [Oheka Castle, inspirationFor, fictional estates in popular culture]
-
A.
inspiration
chosen
Indicates that one entity serves as a motivating or creative influence that stimulates ideas, actions, or feelings in another entity.
-
B.
coPilotWith
Indicates that two entities jointly serve as pilots or share piloting responsibilities for the same vehicle or mission.
-
C.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
D.
inspiredDocument
Indicates that one entity (often a work, idea, or person) served as the creative or conceptual inspiration for the creation or content of another document.
-
E.
inspiredEvent
Indicates that one event served as the motivation, cause, or creative stimulus for another event to occur or be conceived.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4986250508190ac91cfdf7d57073d |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b8098481908097228db8ad0262 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.