Triple
T196685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taisho era |
E3831
|
entity |
| Predicate | technologyTrend |
P7517
|
FINISHED |
| Object | spread of railways |
—
|
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: spread of railways | Statement: [Taisho era, technologyTrend, spread of railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyTrend Context triple: [Taisho era, technologyTrend, spread of railways]
-
A.
technologyParadigm
Indicates a relationship where one entity represents or defines the overarching technological model, framework, or approach within which another entity operates or is categorized.
-
B.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
C.
technologyLevel
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
-
D.
innovation
Indicates the introduction or development of something new or significantly improved compared to existing methods, products, or ideas.
-
E.
associatedWithTechnology
Indicates a relationship where an entity is connected to, involved with, or utilizes a particular technology.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a2598594388190a56f36fa036eac84 |
completed | Feb. 28, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69a25677da14819094cd02868fd30c83 |
completed | Feb. 28, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69a258b30f6c8190be2181f30c40e04d |
completed | Feb. 28, 2026, 2:53 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.