Triple
T38623470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D. Lothrop Company |
E936937
|
entity |
| Predicate | publishingPhilosophy |
P201772
|
FINISHED |
| Object | emphasis on moral instruction |
—
|
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: emphasis on moral instruction | Statement: [D. Lothrop Company, publishingPhilosophy, emphasis on moral instruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishingPhilosophy Context triple: [D. Lothrop Company, publishingPhilosophy, emphasis on moral instruction]
-
A.
publishingPurpose
Indicates the intended goal or reason for which something is being published.
-
B.
publishingModel
Indicates the method or framework by which content is produced, distributed, and made publicly available.
-
C.
publishingSector
Indicates a relationship where an entity operates in, is associated with, or belongs to the publishing industry or market segment.
-
D.
publishingPlatform
Indicates that one entity serves as the medium or service through which another entity is published or made publicly available.
-
E.
manifestoPublisher
Indicates that an entity is responsible for publishing or issuing a particular manifesto.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a001cc0ff588190bb7c8a6fd427d02b |
completed | May 10, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_6a001b3ea18c8190aeda7a32b2697490 |
completed | May 10, 2026, 5:44 a.m. |
| PDg | Predicate description generation | batch_6a001cc053ac8190927768a4ecb023b9 |
completed | May 10, 2026, 5:50 a.m. |
Created at: May 3, 2026, 4:32 p.m.