Triple
T30890685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nixie of the Mill-Pond |
E786887
|
entity |
| Predicate | ATUTypeLabel |
P21560
|
FINISHED |
| Object | The Nix of the Mill-Pond |
—
|
NE NERFINISHED |
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: The Nix of the Mill-Pond | Statement: [The Nixie of the Mill-Pond, ATUTypeLabel, The Nix of the Mill-Pond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ATUTypeLabel Context triple: [The Nixie of the Mill-Pond, ATUTypeLabel, The Nix of the Mill-Pond]
-
A.
ATUType
Indicates a classification relationship where an item is assigned a specific Aarne–Thompson–Uther (ATU) folktale type.
-
B.
labelingType
Indicates the specific kind or category of labeling applied to an entity or between entities, such as the method, standard, or purpose of the label.
-
C.
labelOf
chosen
Indicates that one entity serves as the name, tag, or identifying label assigned to another entity.
-
D.
attributeType
Indicates that one entity specifies the kind or category of attribute that characterizes another entity.
-
E.
labelCatalogType
Indicates that an entity is assigned a specific catalog type label, defining its classification within a cataloging system.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69208e9cc8190a88edc0d9cf1449d |
completed | May 3, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.