Triple

T439852
Position Surface form Disambiguated ID Type / Status
Subject Espionage Act of 1917 E10089 entity
Predicate hasBeenAmended P5571 FINISHED
Object true 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: true | Statement: [Espionage Act of 1917, hasBeenAmended, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBeenAmended
Context triple: [Espionage Act of 1917, hasBeenAmended, true]
  • A. hasAmendments chosen
    Indicates that one entity (such as a document, law, or agreement) includes or is associated with one or more modifications, changes, or additions made after its original creation.
  • B. amendedBy
    Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
  • C. partiallyAmendedBy
    Indicates that an existing item (such as a document, law, or agreement) has been modified in part, but not completely replaced, by another item.
  • D. cannotBeAmendedInRespectOf
    Indicates that a particular item (such as a term, provision, or condition) is not allowed to be changed or modified in the specified respect or aspect.
  • E. amendmentRequires
    Indicates that a particular amendment is necessary or must be applied in relation to another item, document, 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_69a2e8465ef481909655c681b01e2986 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2ef2977888190a0590b2c1bd2f5da completed Feb. 28, 2026, 1:35 p.m.
PD Predicate disambiguation batch_69a2eddcf50c8190bfa0d1f8ee9f604a completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.