Triple
T38067585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Βάτεια |
E950512
|
entity |
| Predicate | hasSpouseRoleInMyth |
P106611
|
FINISHED |
| Object | founder-hero |
—
|
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: founder-hero | Statement: [Βάτεια, hasSpouseRoleInMyth, founder-hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseRoleInMyth Context triple: [Βάτεια, hasSpouseRoleInMyth, founder-hero]
-
A.
hasSpouseInStory
Indicates that one entity is depicted as the spouse of another within the context of a particular story or narrative.
-
B.
spouseOfRole
chosen
Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
-
C.
hasCollaborativeRoleWithSpouse
Indicates that an individual shares a joint, cooperative role or responsibility together with their spouse.
-
D.
hasSpouseDescribed
Indicates that one entity is described as the spouse of another entity.
-
E.
hasSpouseInLineage
Indicates that one entity has, within its ancestral or descendant line, another entity who is or was their spouse.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 3, 2026, 4:21 p.m.