Triple
T18127608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dow Theory |
E433917
|
entity |
| Predicate | trendClassification |
P5318
|
FINISHED |
| Object | primary trend |
—
|
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: primary trend | Statement: [Dow Theory, trendClassification, primary trend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trendClassification Context triple: [Dow Theory, trendClassification, primary trend]
-
A.
marketClassification
Indicates how an entity is categorized or segmented within a particular market or market structure.
-
B.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
C.
trends
Indicates that one entity exhibits a general direction of change or development over time in relation to another reference or context.
-
D.
classificationAccordingTo
Indicates that an entity is assigned a particular class, type, or category as defined or determined by a specified source, standard, or authority.
-
E.
classificationConsensus
Indicates that multiple agents or sources agree on the same classification or category assignment for a given entity or item.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddef4cd88190b16ef0d6ed3968c6 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.