Triple
T29701453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbara Pierce |
E751495
|
entity |
| Predicate | relativeNotableWork |
P203535
|
FINISHED |
| Object | Frasier |
E32967
|
NE 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: Frasier | Statement: [Barbara Pierce, relativeNotableWork, Frasier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeNotableWork Context triple: [Barbara Pierce, relativeNotableWork, Frasier]
-
A.
notableWorkWith
Indicates a relationship where two or more entities are recognized for having collaborated on or been jointly associated with a significant work or project.
-
B.
notableWorkIn
Indicates that an entity is known for or associated with a significant work, contribution, or achievement in a particular field or context.
-
C.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
D.
notableWorkAs
Indicates a relationship where a particular work is recognized as a significant or distinguished creation associated with an entity.
-
E.
notableTypeOfWork
Indicates that a work is a significant or defining example within a particular type or category of work associated with an entity.
- F. None of above. chosen
Provenance (5 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a019dfc69fc8190b0d80279a6216ba7 |
completed | May 11, 2026, 9:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a267ed2662081909896d92e22acd52d |
completed | June 8, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_6a019d54586c81908292d4880db9fad2 |
completed | May 11, 2026, 9:11 a.m. |
| PDg | Predicate description generation | batch_6a019dfba430819089f5609d89fbb7d9 |
completed | May 11, 2026, 9:14 a.m. |
Created at: April 28, 2026, 7:24 p.m.