Triple

T423197
Position Surface form Disambiguated ID Type / Status
Subject Schaefer Stadium E8148 entity
Predicate successorFunction P13577 FINISHED
Object site of Gillette Stadium and Patriot Place development area 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: site of Gillette Stadium and Patriot Place development area | Statement: [Schaefer Stadium, successorFunction, site of Gillette Stadium and Patriot Place development area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successorFunction
Context triple: [Schaefer Stadium, successorFunction, site of Gillette Stadium and Patriot Place development area]
  • A. successorState
    Indicates that one state directly follows another as the immediate next state in a sequence or process.
  • B. successorOperator
    Indicates that one operator directly follows another in a defined sequence or ordering.
  • C. successor
    Indicates that one entity directly follows another in an ordered sequence or position.
  • D. eventualSuccessor
    Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
  • E. successorInterface
    Indicates that one interface directly follows and replaces another interface in a sequence or version lineage.
  • 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_69a2e7f1d1bc81909cf2dc9754a3c334 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eec200648190bcb9f1b98c8e9cdf completed Feb. 28, 2026, 1:33 p.m.
PD Predicate disambiguation batch_69a2edd5439c8190aea661b8b4aa51e9 completed Feb. 28, 2026, 1:29 p.m.
PDg Predicate description generation batch_69a2ee8b56d08190bd625626353d01b4 completed Feb. 28, 2026, 1:32 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.