Triple
T25085833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerald Scales |
E628316
|
entity |
| Predicate | significantlyAffects |
P63153
|
FINISHED |
| Object | life of Sophia Baines |
—
|
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: life of Sophia Baines | Statement: [Gerald Scales, significantlyAffects, life of Sophia Baines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantlyAffects Context triple: [Gerald Scales, significantlyAffects, life of Sophia Baines]
-
A.
alsoAffects
Indicates that an action, condition, or change impacting one entity additionally impacts another entity as well.
-
B.
hasSignificantInfluenceIn
chosen
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
-
C.
recognizesImpactOn
Indicates that one entity acknowledges or understands the effect or consequences it has on another entity or situation.
-
D.
canImpact
Indicates that one entity has the potential or ability to affect, influence, or cause a change in another entity.
-
E.
affectsRelationshipBetween
Indicates that one entity causes a change or influence on the nature, quality, or status of the relationship between two or more other entities.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:23 a.m.