Triple
T3664055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of Gold |
E77717
|
entity |
| Predicate | effectOfDrive |
P24726
|
FINISHED |
| Object | causes highly improbable events |
—
|
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: causes highly improbable events | Statement: [Heart of Gold, effectOfDrive, causes highly improbable events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOfDrive Context triple: [Heart of Gold, effectOfDrive, causes highly improbable events]
-
A.
drives
Indicates that one entity operates and controls the movement of a vehicle or similar conveyance transporting themselves or others.
-
B.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
C.
drivingForce
chosen
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
-
D.
driveResult
Indicates the outcome or consequence produced by a driving action or driving-related event.
-
E.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3fe5eb08190ab15044acf9ac8a9 |
completed | March 8, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.