Triple
T25607756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrmidon |
E641958
|
entity |
| Predicate | hasNotableAssociations |
P43975
|
FINISHED |
| Object | Zeus |
—
|
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: Zeus | Statement: [Myrmidon, hasNotableAssociations, Zeus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAssociations Context triple: [Myrmidon, hasNotableAssociations, Zeus]
-
A.
hasNotableAffiliation
Indicates that an entity is significantly associated or connected with another entity, such as an organization, group, or institution, in a way that is noteworthy or distinguished.
-
B.
hasNotableConnectionTo
chosen
Indicates a significant or noteworthy relationship, association, or link exists between two entities.
-
C.
sharesNotableAssociationWith
Indicates a mutual, noteworthy connection or linkage between two entities that is significant enough to be recognized or highlighted.
-
D.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
-
E.
hasNotabilityFor
Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 21, 2026, 4:39 p.m.