Triple

T40630
Position Surface form Disambiguated ID Type / Status
Subject Time Inc. E802 entity
Predicate ownedBrand P1500 FINISHED
Object Fortune E3452 NE 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: Fortune | Statement: [Time Inc., ownedBrand, Fortune]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fortune
Context triple: [Time Inc., ownedBrand, Fortune]
  • A. Fortune chosen
    Fortune is a long-running American business magazine known for its influential rankings such as the Fortune 500 and in-depth coverage of global economics and corporate leadership.
  • B. Veritas
    Veritas is the Latin word for "truth" and is famously used as the motto of Harvard University.
  • C. Excelsior
    Excelsior is the Latin state motto of New York, meaning "ever upward" and symbolizing aspiration and continual progress.
  • D. Porter
    Porter is a transit station in Cambridge, Massachusetts that serves both MBTA commuter rail and Red Line subway services.
  • E. Eureka
    Eureka is a historic coastal city in Northern California known for its Victorian architecture, maritime heritage, and role as a regional cultural and economic center.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a247a8f6c08190bac804906d62ed5a completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a24ec1ef5481909daf99654dfa3f57 completed Feb. 28, 2026, 2:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69a255338b6c8190bb31101691ce689a completed Feb. 28, 2026, 2:38 a.m.
Created at: Feb. 28, 2026, 1:46 a.m.