Triple
T10489249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amalthea |
E247370
|
entity |
| Predicate | sometimesIdentifiedAs |
P86837
|
FINISHED |
| Object | goat who suckled Zeus |
—
|
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: goat who suckled Zeus | Statement: [Amalthea, sometimesIdentifiedAs, goat who suckled Zeus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesIdentifiedAs Context triple: [Amalthea, sometimesIdentifiedAs, goat who suckled Zeus]
-
A.
knownAsOneOf
Indicates that an entity is recognized or referred to as one member of a specified set of alternative names, labels, or identities.
-
B.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
C.
commonlyIdentifiedWith
chosen
Indicates that two entities are widely regarded or treated as the same or equivalent, even if they are formally distinct.
-
D.
alsoKnownAs
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
E.
alsoKnownThrough
Indicates that an entity is recognized or identified by means of another entity, such as a source, context, or intermediary, through which its alternative name or identity is known.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097ca5c081908b47a08ca7885650 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.