Triple
T33561900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clemens |
E859644
|
entity |
| Predicate | confidesPastTo |
P33486
|
FINISHED |
| Object | Ellen Ripley |
—
|
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: Ellen Ripley | Statement: [Clemens, confidesPastTo, Ellen Ripley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confidesPastTo Context triple: [Clemens, confidesPastTo, Ellen Ripley]
-
A.
confidesIn
chosen
Indicates that one entity shares private, sensitive, or personal information or feelings with another entity in trust.
-
B.
confidantOf
Indicates a relationship in which one entity is trusted by another to receive and keep personal, private, or sensitive information.
-
C.
confessedTo
Indicates that one entity admitted guilt or revealed the truth about an action, wrongdoing, or secret to another entity.
-
D.
confessedAs
Indicates that one entity has admitted or acknowledged being or doing something, typically revealing guilt, identity, or involvement in relation to another entity.
-
E.
confesses
Indicates that one entity openly admits or acknowledges something, typically a wrongdoing, secret, or previously concealed fact, to another entity.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:40 a.m.