Triple
T38092723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmony Node 2 |
E951154
|
entity |
| Predicate | hasHatches |
P190567
|
FINISHED |
| Object | six |
—
|
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: six | Statement: [Harmony Node 2, hasHatches, six]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHatches Context triple: [Harmony Node 2, hasHatches, six]
-
A.
hasHatch
Indicates that one entity possesses or is equipped with a hatch, such as an opening or access panel.
-
B.
hatchesIn
Indicates that one entity emerges or is born from an egg within or during the environment, location, or context specified by another entity.
-
C.
hatchesFrom
Indicates that one entity emerges or is born by breaking out from within another entity, typically an egg or encasing structure.
-
D.
hatchType
Indicates the specific manner or category of hatching by which something (typically an egg or similar entity) opens or produces offspring.
-
E.
eggHatchedBy
Indicates that an egg is brought to hatching by a specific agent or entity.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:21 p.m.