Triple
T19818135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ofglen |
E476112
|
entity |
| Predicate | relationshipToOffred |
P137436
|
FINISHED |
| Object | shopping partner |
—
|
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: shopping partner | Statement: [Ofglen, relationshipToOffred, shopping partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToOffred Context triple: [Ofglen, relationshipToOffred, shopping partner]
-
A.
relationshipWithHumbertHumbert
Indicates that an entity has a specified type of personal, emotional, or social relationship with Humbert Humbert.
-
B.
relationshipToGregorSamsa
Indicates the specific familial, social, or personal relationship that one entity has to Gregor Samsa.
-
C.
relationshipToCelie
Indicates a relational connection that someone or something has specifically with Celie, such as their role, bond, or association to her.
-
D.
relationshipToPatsey
Indicates the nature or type of relationship an entity has with the person or entity named Patsey.
-
E.
relationshipTypeWithAibileenClark
Indicates the specific type or nature of the relationship that an entity has with Aibileen Clark.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fac7b481909a19ae0d608e01d9 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:50 p.m.