Triple
T10627514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salmacis |
E250359
|
entity |
| Predicate | relationshipToHermaphroditus |
P95067
|
FINISHED |
| Object | lover |
—
|
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: lover | Statement: [Salmacis, relationshipToHermaphroditus, lover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToHermaphroditus Context triple: [Salmacis, relationshipToHermaphroditus, lover]
-
A.
opusRelationship
Indicates a relationship between creative works (opuses), such as versions, adaptations, or parts within a larger compositional whole.
-
B.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
C.
hermaphroditeChromosomes
Indicates that an entity possesses a chromosomal configuration associated with hermaphroditic sexual characteristics or functions.
-
D.
reproductiveRole
Indicates the specific function or part an entity plays in biological reproduction within a reproductive process or system.
-
E.
relationshipWithHumbertHumbert
Indicates that an entity has a specified type of personal, emotional, or social relationship with Humbert Humbert.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df8207f08190a6362a8ba00988b2 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 8:55 p.m.