Triple
T27795530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Feynman bibliography |
E701197
|
entity |
| Predicate | documentsContributionType |
P143309
|
FINISHED |
| Object | theoretical physics |
—
|
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: theoretical physics | Statement: [Richard Feynman bibliography, documentsContributionType, theoretical physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentsContributionType Context triple: [Richard Feynman bibliography, documentsContributionType, theoretical physics]
-
A.
documentsTypeOfWork
chosen
Indicates that one entity records or specifies the category or type of work associated with another entity.
-
B.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
C.
documentsActivity
Indicates that one entity records, describes, or provides evidence of an activity performed by another entity.
-
D.
documentsTypeOfStructure
Indicates that an entity records or specifies the particular type or classification of a structure.
-
E.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
- 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_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 5:31 p.m.