Triple
T32334121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letters from a Self-Made Merchant to His Son |
E826125
|
entity |
| Predicate | targetValues |
P164961
|
FINISHED |
| Object | honesty in business |
—
|
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: honesty in business | Statement: [Letters from a Self-Made Merchant to His Son, targetValues, honesty in business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetValues Context triple: [Letters from a Self-Made Merchant to His Son, targetValues, honesty in business]
-
A.
targetsVector
Indicates that one entity is directed toward, aimed at, or focused on another entity represented as a vector (e.g., a direction or target position).
-
B.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
goalValue
chosen
Indicates the target or desired value that an entity aims to achieve or reach.
-
D.
evaluationTarget
Indicates that something is the object, subject, or focus being assessed, judged, or analyzed in an evaluation process.
-
E.
targetsField
Indicates that one entity is directed toward, focuses on, or is intended to affect a specific field or attribute of another entity.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 1, 2026, 12:48 a.m.