Triple
T36325206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean |
E894447
|
entity |
| Predicate | hasChildInWork |
P198637
|
FINISHED |
| Object | Liam |
—
|
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: Liam | Statement: [Jean, hasChildInWork, Liam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildInWork Context triple: [Jean, hasChildInWork, Liam]
-
A.
hasParentWork
Indicates that one work is derived from, contained within, or otherwise subordinate to another, more primary work.
-
B.
hasChildIn
Indicates that one entity has a child who is located in, associated with, or present within another specified entity or context.
-
C.
hasParentWorkKey
Indicates that an entity is associated with the identifier (key) of the parent work from which it is derived or of which it is a part.
-
D.
isChildIn
Indicates that one entity is the child (offspring or subordinate in a family or hierarchical structure) of another entity.
-
E.
hasChildCollaborator
Indicates that an entity has another entity as a collaborator in a subordinate, dependent, or derivative role.
- 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_69f76e4dcf088190a6c3216c209cab52 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_69fef8c2cdd881908c6f44e4dfa5ffd0 |
completed | May 9, 2026, 9:05 a.m. |
Created at: May 3, 2026, 4:09 p.m.