Triple
T16856381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perdita |
E409793
|
entity |
| Predicate | relationshipToPolixenes |
P125253
|
FINISHED |
| Object | future daughter-in-law |
—
|
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: future daughter-in-law | Statement: [Perdita, relationshipToPolixenes, future daughter-in-law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToPolixenes Context triple: [Perdita, relationshipToPolixenes, future daughter-in-law]
-
A.
relationshipToTrinculo
Indicates the specific type of relationship or connection that one entity has to the entity named Trinculo.
-
B.
relationshipWithCaliban
Indicates a relationship or connection that an entity has with Caliban, without specifying the type or nature of that relationship.
-
C.
relationshipToDeianira
Indicates a specified type of relationship that one entity has to Deianira, such as familial, romantic, or social connection.
-
D.
relationshipToCaliban
Indicates the specific type of relationship or connection that one entity has to the entity named Caliban.
-
E.
relationshipToHeracles
Indicates the specific familial or social relationship that an entity has to Heracles.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37d69a08190af18b421066f44f1 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:24 a.m.