Triple
T7067634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnival Row |
E164597
|
entity |
| Predicate | hasMythologicalCreatures |
P45276
|
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: [Carnival Row, hasMythologicalCreatures, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythologicalCreatures Context triple: [Carnival Row, hasMythologicalCreatures, yes]
-
A.
hasMythologicalFeature
chosen
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
B.
hasSimilarMythicalCreature
Indicates that two entities are associated with mythical creatures that share comparable characteristics, roles, or symbolic meanings.
-
C.
hasMythologicalOpponents
Indicates that one entity is opposed or challenged by another entity within a mythological or legendary context.
-
D.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
E.
linkedToMythology
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a737dc8190add7f0228cb28111 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:39 p.m.