Triple

T92582
Position Surface form Disambiguated ID Type / Status
Subject Stumptown E1860 entity
Predicate hasOriginReason P708 FINISHED
Object rapid 19th-century growth of Portland, Oregon 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: rapid 19th-century growth of Portland, Oregon | Statement: [Stumptown, hasOriginReason, rapid 19th-century growth of Portland, Oregon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOriginReason
Context triple: [Stumptown, hasOriginReason, rapid 19th-century growth of Portland, Oregon]
  • A. hasNameOrigin
    Indicates that the origin or source of an entity’s name is specified by the related entity.
  • B. hasCause chosen
    Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
  • C. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • D. hasOriginalJurisdictionOver
    Indicates that a legal body or authority has the power to hear and decide a case first, before any appellate review by higher bodies.
  • E. appliedBecauseOf
    Indicates that one entity is applied, used, or enacted as a consequence or result of another specified cause or condition.
  • 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_69a24d1a97dc819094e6c021fe9b05a7 completed Feb. 28, 2026, 2:04 a.m.
NER Named-entity recognition batch_69a2512ef600819084d3c627f0d534f4 completed Feb. 28, 2026, 2:21 a.m.
PD Predicate disambiguation batch_69a24eb9a5ac8190b1d1300e8c4e3606 completed Feb. 28, 2026, 2:11 a.m.
Created at: Feb. 28, 2026, 2:07 a.m.