Triple

T31369
Position Surface form Disambiguated ID Type / Status
Subject United States Statutes at Large E625 entity
Predicate compilationMethod P859 FINISHED
Object session-by-session compilation of enacted laws 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: session-by-session compilation of enacted laws | Statement: [United States Statutes at Large, compilationMethod, session-by-session compilation of enacted laws]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: compilationMethod
Context triple: [United States Statutes at Large, compilationMethod, session-by-session compilation of enacted laws]
  • A. usesComputationMethod
    Indicates that an entity performs its processing or decision-making by applying a specified computational method or algorithm.
  • B. constructionMethod
    Indicates the technique or process by which something is built, assembled, or created.
  • C. codifiedIn
    Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
  • D. method chosen
    Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
  • E. programmingLanguage
    Indicates that one entity is a programming language used to create, control, or interact with the other entity.
  • 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_69a2479dec388190967ba648663442c9 completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a249ec0d288190ac3a0939db61813b completed Feb. 28, 2026, 1:50 a.m.
PD Predicate disambiguation batch_69a24870417081909c7c01e400c94716 completed Feb. 28, 2026, 1:44 a.m.
Created at: Feb. 28, 2026, 1:44 a.m.