Triple
T28640040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niobe in Rome |
E724894
|
entity |
| Predicate | hasSecretLover |
P23617
|
FINISHED |
| Object | Evander Pulchio |
—
|
NE NERFINISHED |
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: Evander Pulchio | Statement: [Niobe in Rome, hasSecretLover, Evander Pulchio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecretLover Context triple: [Niobe in Rome, hasSecretLover, Evander Pulchio]
-
A.
hasSecretMarriageWith
Indicates a relationship where two entities are secretly married to each other, with the marriage intentionally concealed from others.
-
B.
hasAffairWith
chosen
Indicates that one entity is engaged in a secret or illicit romantic or sexual relationship with another entity, typically outside a committed partnership.
-
C.
secretlyIs
Indicates that one entity possesses a hidden or undisclosed identity, role, or attribute in relation to another entity.
-
D.
hasConcubineFrom
Indicates that a person has a concubine whose origin or affiliation is from a specified place or source.
-
E.
hasBoyfriend
Indicates that a person is in a romantic relationship where the other party is their boyfriend.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 28, 2026, 4:43 a.m.