Triple

T27378644
Position Surface form Disambiguated ID Type / Status
Subject Springfield, New Jersey E691149 entity
Predicate hasRevolutionaryWarSignificance P4345 FINISHED
Object yes 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: yes | Statement: [Springfield, New Jersey, hasRevolutionaryWarSignificance, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRevolutionaryWarSignificance
Context triple: [Springfield, New Jersey, hasRevolutionaryWarSignificance, yes]
  • A. hasWarOfIndependenceRole
    Indicates that an entity held a specific role or position in the context of a war of independence.
  • B. onlyRevolutionaryWarBattleEntirelyOn
    Indicates that the referenced battle is the sole Revolutionary War engagement fought entirely within the specified location or context.
  • C. hasMilitarySignificance
    Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
  • D. hasHistoricalSignificance chosen
    Indicates that something possesses notable importance or influence within a historical context or period.
  • E. hasIndependenceMovementSignificance
    Indicates that something plays an important role or holds notable relevance in the context of an independence movement.
  • 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_69ef52022538819081f873d0c84a6dd6 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69feafa1ba0081909013800b85a9f613 completed May 9, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69feae58d62c81909d031f3df8992883 completed May 9, 2026, 3:47 a.m.
Created at: April 27, 2026, 12:21 p.m.