Triple
T3658410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echidna |
E77589
|
entity |
| Predicate | notableChildrenGroup |
P50188
|
FINISHED |
| Object | monsters slain by Greek heroes |
—
|
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: monsters slain by Greek heroes | Statement: [Echidna, notableChildrenGroup, monsters slain by Greek heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableChildrenGroup Context triple: [Echidna, notableChildrenGroup, monsters slain by Greek heroes]
-
A.
notableSubgroup
Indicates that one group forms a particularly significant or noteworthy subset within a larger group.
-
B.
childNotableFor
Indicates that a child is recognized or distinguished for a particular achievement, role, or characteristic.
-
C.
notableCharacterGroup
Indicates that a group of characters is especially prominent, significant, or noteworthy within a given context or work.
-
D.
childGroup
Indicates that one group is a subordinate or contained subgroup (child) of another group (parent) within a hierarchical structure.
-
E.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d48a2081908ac0f76d548a53ee |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb97cdb788190a5ce96b21bd157ab |
completed | March 8, 2026, 6:01 p.m. |
Created at: March 8, 2026, 3:24 p.m.