Triple
T27795512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Feynman bibliography |
E701197
|
entity |
| Predicate | coversWorkType |
P126481
|
FINISHED |
| Object | scientific papers |
—
|
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: scientific papers | Statement: [Richard Feynman bibliography, coversWorkType, scientific papers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversWorkType Context triple: [Richard Feynman bibliography, coversWorkType, scientific papers]
-
A.
workCovered
Indicates that one work or effort is included within the scope, protection, or responsibility defined by another entity or arrangement.
-
B.
featuresWorkType
chosen
Indicates that an entity includes, supports, or is characterized by a particular type or category of work.
-
C.
coverOfWorkBy
Indicates that one work is a cover version or performance of another work originally created by a specified creator or artist.
-
D.
workCoverage
Indicates that one entity’s work or responsibilities extend to, include, or provide coverage for another entity, area, or time period.
-
E.
associatedWorkType
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 27, 2026, 5:31 p.m.