Triple
T33107929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JohnsPrayerForHealthAndWellBeing |
E847242
|
entity |
| Predicate | hasPrimaryPetitioner |
P152662
|
FINISHED |
| Object | John |
—
|
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: John | Statement: [JohnsPrayerForHealthAndWellBeing, hasPrimaryPetitioner, John]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryPetitioner Context triple: [JohnsPrayerForHealthAndWellBeing, hasPrimaryPetitioner, John]
-
A.
casePetitioner
chosen
Indicates that an entity is the party who formally brings or initiates a legal case or petition before a court or tribunal.
-
B.
hasPrimaryAppeal
Indicates that one entity serves as the main or most important attraction, interest, or persuasive feature for another entity.
-
C.
hasMainDefendant
Indicates that a legal case or proceeding identifies a specific individual or entity as its primary defendant.
-
D.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
E.
hasPetOwner
Indicates that a person or entity serves as the owner or caretaker of a particular pet.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0160834e388190908591b300954d29 |
completed | May 11, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a01602a83408190a11d754bdc7da0e9 |
completed | May 11, 2026, 4:50 a.m. |
Created at: May 1, 2026, 1:26 a.m.