Triple
T20245869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herpyllis of Stagira |
E498422
|
entity |
| Predicate | relationshipToNicomachus |
P74793
|
FINISHED |
| Object | mother |
—
|
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: mother | Statement: [Herpyllis of Stagira, relationshipToNicomachus, mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToNicomachus Context triple: [Herpyllis of Stagira, relationshipToNicomachus, mother]
-
A.
philosophicalRelationTo
Indicates a conceptual or theoretical connection one entity holds toward another within a philosophical framework or viewpoint.
-
B.
النسب
chosen
Indicates a genealogical or familial relationship linking one entity to another through lineage or descent.
-
C.
relationshipToOtherSefirot
Indicates how one sefirah is connected or related to other sefirot within the overall structure or network of sefirot.
-
D.
relationshipToHeracles
Indicates the specific familial or social relationship that an entity has to Heracles.
-
E.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a26c8481908f408fb6426aece9 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.