Triple
T19981561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phebe |
E493826
|
entity |
| Predicate | relationshipToRosalind |
P138165
|
FINISHED |
| Object | infatuated with Rosalind in disguise as Ganymede |
—
|
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: infatuated with Rosalind in disguise as Ganymede | Statement: [Phebe, relationshipToRosalind, infatuated with Rosalind in disguise as Ganymede]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToRosalind Context triple: [Phebe, relationshipToRosalind, infatuated with Rosalind in disguise as Ganymede]
-
A.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
B.
relationToCurie
Indicates a relational connection or association that one entity has specifically with Curie.
-
C.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
D.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
E.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
- F. None of above. chosen
Provenance (4 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d13a8a88190bf5f4f697793f4c9 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:28 p.m.