Triple
T28826193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Parker |
E727910
|
entity |
| Predicate | relativeInWork |
P199923
|
FINISHED |
| Object | Parker family |
—
|
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: Parker family | Statement: [Arthur Parker, relativeInWork, Parker family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeInWork Context triple: [Arthur Parker, relativeInWork, Parker family]
-
A.
isContainedInWorkBy
Indicates that something is included within, or forms a part of, a larger work created by a specified agent.
-
B.
workWithin
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined by another entity.
-
C.
relatedWorkForm
Indicates a relationship in which one work is connected to another through a different form or version (e.g., adaptation, translation, or other format variation).
-
D.
associatedWithInWork
chosen
Indicates that two entities are connected or related to each other within the context of a particular work or project.
-
E.
positionInWork
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: April 28, 2026, 6:36 a.m.