Triple
T23193500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Harry Weston |
E579810
|
entity |
| Predicate | parentStatus |
P112368
|
FINISHED |
| Object | single father |
—
|
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: single father | Statement: [Dr. Harry Weston, parentStatus, single father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentStatus Context triple: [Dr. Harry Weston, parentStatus, single father]
-
A.
parentsStatus
chosen
Indicates the marital or relational status between a person's parents (e.g., married, divorced, separated, single).
-
B.
parentService
Indicates that one service functions as the higher-level or owning service in relation to another, which depends on or is derived from it.
-
C.
parent
Indicates a relationship where one entity is the direct mother or father of another entity, from whom that other entity is descended.
-
D.
parentDetermination
Indicates that one entity is responsible for determining, designating, or establishing the parent or parental status of another entity.
-
E.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd971d08190a132d24094e0c37b |
completed | April 29, 2026, 4:58 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:06 p.m.