Triple
T28155871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timothy Green |
E714744
|
entity |
| Predicate | adoptiveParentsInStory |
P37844
|
FINISHED |
| Object | Jim Green |
—
|
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: Jim Green | Statement: [Timothy Green, adoptiveParentsInStory, Jim Green]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptiveParentsInStory Context triple: [Timothy Green, adoptiveParentsInStory, Jim Green]
-
A.
adoptiveParent
chosen
Indicates that one entity is the legally recognized parent of another through adoption rather than biological descent.
-
B.
adoptiveFamily
Indicates a familial relationship formed through legal adoption rather than biological descent.
-
C.
adoptiveChild
Indicates that one entity is the child of another through legal adoption rather than biological descent.
-
D.
adoptiveHome
Indicates that an entity serves as the adoptive home or placement setting for another entity, typically a child or animal, following an adoption process.
-
E.
adoptiveStructure
Indicates a structural relationship where one entity has been adopted into, or functions as, the adopted counterpart of another entity within a system or hierarchy.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 10:02 p.m.