Triple
T26357115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taynitskaya Tower |
E663093
|
entity |
| Predicate | hasSecretPassage |
P108779
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Taynitskaya Tower, hasSecretPassage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecretPassage Context triple: [Taynitskaya Tower, hasSecretPassage, yes]
-
A.
hasSecretExits
Indicates that an entity possesses one or more hidden or concealed exits that are not part of its normal, visible access points.
-
B.
hasSecretArea
Indicates that an entity contains or is associated with a hidden or restricted area not normally accessible or visible.
-
C.
hasSecretExit
chosen
Indicates that something includes or is connected to a hidden or concealed way out.
-
D.
hasKeyPassage
Indicates that one entity contains or includes a particularly important or central passage relevant to another entity.
-
E.
containsSecretRoomCount
Indicates that an entity has a specified number of secret rooms contained within it.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 26, 2026, 10:49 p.m.