Triple
T33812052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cros-ny-Cuirn |
E866561
|
entity |
| Predicate | openingStatusInFiction |
P13811
|
FINISHED |
| Object | open |
—
|
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: open | Statement: [Cros-ny-Cuirn, openingStatusInFiction, open]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingStatusInFiction Context triple: [Cros-ny-Cuirn, openingStatusInFiction, open]
-
A.
fictionalStatus
Indicates that an entity exists only in imagination or narrative and does not correspond to a real-world counterpart.
-
B.
eraWithinFiction
Indicates that a time period or era exists inside the narrative world or timeline of a fictional work.
-
C.
showWithinFiction
Indicates that one entity is depicted, referenced, or occurs as part of the fictional world or narrative context of another entity.
-
D.
stateInFiction
chosen
Indicates that a particular state or condition exists within a fictional context or narrative world rather than in real-world actuality.
-
E.
guardedByInFiction
Indicates that one fictional entity is protected or watched over by another within a narrative context.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:46 a.m.