Triple
T65904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Physical Review |
E1312
|
entity |
| Predicate | hasDigitalArchive |
P4467
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Physical Review, hasDigitalArchive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalArchive Context triple: [Physical Review, hasDigitalArchive, true]
-
A.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
B.
hasDeweyDecimalClassification
Indicates that an item (such as a book or resource) is assigned a specific Dewey Decimal Classification number representing its subject area in a library system.
-
C.
hasDigitalInitiative
Indicates that an entity is engaged in or associated with a specific digital project, program, or transformation effort.
-
D.
archivesType
Indicates that one entity serves as an archival record or stored version of another entity, specifying the type or category of that archived content.
-
E.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2516eda54819090f5c14384d4eab1 |
completed | Feb. 28, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69a24ea5c140819080409a968c8d2ce8 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a2516d98e88190b79261bd3fcadd9b |
completed | Feb. 28, 2026, 2:22 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.