Triple

T20718586
Position Surface form Disambiguated ID Type / Status
Subject New Brunswick Route 2 E509245 entity
Predicate formerAlignmentReplacedBy P29646 FINISHED
Object new controlled-access alignment 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: new controlled-access alignment | Statement: [New Brunswick Route 2, formerAlignmentReplacedBy, new controlled-access alignment]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formerAlignmentReplacedBy
Context triple: [New Brunswick Route 2, formerAlignmentReplacedBy, new controlled-access alignment]
  • A. realignedFrom
    Indicates that something has been adjusted or repositioned from a previous alignment, configuration, or orientation to a new one.
  • B. placedBy
    Indicates that one entity was positioned, set, or put in a location or context by another entity.
  • C. replacedWith chosen
    Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
  • D. alignmentChange
    Indicates a change in the moral, ethical, or factional stance of an entity relative to its previous alignment.
  • E. realignedOn
    Indicates that something has been adjusted or repositioned so that it is now aligned with a specified reference or standard.
  • 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_69e0b4c4cc648190b45fda6e2b20af56 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c1d39bec8190b3642b0d6d833375 completed April 21, 2026, 12:16 a.m.
PD Predicate disambiguation batch_69e5c04b31248190b9b9d91b5cb854e3 completed April 20, 2026, 5:57 a.m.
Created at: April 16, 2026, 12:25 p.m.