Triple
T4238102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hera Parthenos |
E94742
|
entity |
| Predicate | relatedToEpithet |
P23283
|
FINISHED |
| Object | Parthenos as used for Athena |
—
|
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: Parthenos as used for Athena | Statement: [Hera Parthenos, relatedToEpithet, Parthenos as used for Athena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToEpithet Context triple: [Hera Parthenos, relatedToEpithet, Parthenos as used for Athena]
-
A.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
C.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
D.
etymologyRelatesTo
Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
-
E.
epithetOrTitle
chosen
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e7589b48190a16e7ff29fb6a162 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.