Triple
T1070917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sister Margaret |
E23325
|
entity |
| Predicate | drivingMotivation |
P6699
|
FINISHED |
| Object | faith in God |
—
|
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: faith in God | Statement: [Sister Margaret, drivingMotivation, faith in God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingMotivation Context triple: [Sister Margaret, drivingMotivation, faith in God]
-
A.
motivationFor
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
B.
drives
Indicates that one entity operates and controls the movement of a vehicle or similar conveyance transporting themselves or others.
-
C.
motive
chosen
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
D.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
E.
motivated
Indicates that one entity provides a reason, drive, or incentive that causes another entity to act or behave in a certain way.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b92848148190ba8795cb8d0a1d0a |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73844708190a16c9e9824ca2fb6 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.