Triple
T37774791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wieża i inne opowiadania |
E941654
|
entity |
| Predicate | hasExistentialDimension |
P194289
|
FINISHED |
| Object | tak |
—
|
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: tak | Statement: [Wieża i inne opowiadania, hasExistentialDimension, tak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExistentialDimension Context triple: [Wieża i inne opowiadania, hasExistentialDimension, tak]
-
A.
hasExistentiale
Indicates that an entity possesses or is associated with an existential characteristic, condition, or mode of being.
-
B.
hasDimensionality
Indicates that an entity possesses a specific number of dimensions or a particular dimensional structure.
-
C.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
D.
hasIndividualDimension
Indicates that an entity possesses a specific, separately identifiable dimension or measurable extent as an individual attribute.
-
E.
includesDimension
Indicates that one entity encompasses or contains a particular dimension or measurable aspect as part of its definition or structure.
- F. None of above. chosen
Provenance (4 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: May 3, 2026, 4:19 p.m.