Triple
T33314477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Just Me |
E852976
|
entity |
| Predicate | hasSpouseDiscussed |
P195151
|
FINISHED |
| Object | John Thaw |
—
|
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 Thaw | Statement: [Just Me, hasSpouseDiscussed, John Thaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseDiscussed Context triple: [Just Me, hasSpouseDiscussed, John Thaw]
-
A.
hasSpouseDescribed
Indicates that one entity is described as the spouse of another entity.
-
B.
spouseInvolvedIn
Indicates that a person's spouse participates in, is associated with, or plays a role in a specified activity, event, or situation.
-
C.
hasSpouseInStory
Indicates that one entity is depicted as the spouse of another within the context of a particular story or narrative.
-
D.
spouseInQuestion
Indicates that the referenced person is the spouse of the primary entity being discussed or queried.
-
E.
hasCollaborativeRoleWithSpouse
Indicates that an individual shares a joint, cooperative role or responsibility together with their spouse.
- F. None of above. chosen
Provenance (4 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
| PDg | Predicate description generation | batch_69fda945e1e08190bf923fcd4d2c548a |
completed | May 8, 2026, 9:13 a.m. |
Created at: May 1, 2026, 1:33 a.m.