Triple

T322417
Position Surface form Disambiguated ID Type / Status
Subject TMS E6441 entity
Predicate logicLevelDetermines P11422 FINISHED
Object next TAP controller state 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: next TAP controller state | Statement: [TMS, logicLevelDetermines, next TAP controller state]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: logicLevelDetermines
Context triple: [TMS, logicLevelDetermines, next TAP controller state]
  • A. logicSystem
    Indicates a relationship where an entity is associated with, defined within, or governed by a particular logical framework or system of formal reasoning.
  • B. meetsAtLevel
    Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
  • C. hasLevel
    Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
  • D. classificationLevel
    Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
  • E. legalAuthorityLevel
    Indicates the degree or rank of formal legal power or jurisdiction an entity holds in relation to another or within a given context.
  • 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_69a2e7933d6c8190bb2592ad13286ef2 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2ea81a1e88190b3496070eb3d85f5 completed Feb. 28, 2026, 1:15 p.m.
PD Predicate disambiguation batch_69a2e948048c819098ba4de9261ef2ef completed Feb. 28, 2026, 1:10 p.m.
PDg Predicate description generation batch_69a2ea09a5e881908b313cb37409a4f9 completed Feb. 28, 2026, 1:13 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.