Triple
T8389995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Austen (brother) |
E197916
|
entity |
| Predicate | livedApartFromFamily |
P81950
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [George Austen (brother), livedApartFromFamily, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livedApartFromFamily Context triple: [George Austen (brother), livedApartFromFamily, true]
-
A.
livedWith
Indicates that two entities shared the same residence or household for a period of time.
-
B.
hasFamilyHomeAt
Indicates that an entity has its family residence or primary household located at a specified place.
-
C.
returnedToFamilyHomeBy
Indicates that an entity has been brought or taken back to their family home by another specified entity.
-
D.
hasParentHouse
Indicates that an entity is associated with or belongs to a specific parent house within a hierarchical or familial structure.
-
E.
familyInvolvement
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb810ac380819095bd67f0555ac2a8 |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:03 p.m.