Triple
T34248820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve Rand |
E878675
|
entity |
| Predicate | relationshipToChance |
P193873
|
FINISHED |
| Object | benefactor |
—
|
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: benefactor | Statement: [Eve Rand, relationshipToChance, benefactor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToChance Context triple: [Eve Rand, relationshipToChance, benefactor]
-
A.
relationshipToHopeChance
Indicates a relationship in which one entity is connected to another through hope, likelihood, or expectation of a possible outcome.
-
B.
relationshipToBurtChance
chosen
Indicates the specific familial, social, or professional relationship that one entity has to Burt Chance.
-
C.
relationshipToHeed
Indicates a relationship in which one entity is expected to pay attention to, respect, or follow the guidance, warnings, or wishes of another entity.
-
D.
relationshipImpact
Indicates how one entity’s relationship with another affects or changes those entities or their interaction.
-
E.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.