Triple

T10851750
Position Surface form Disambiguated ID Type / Status
Subject Assignment Expressions E256161 entity
Predicate notAllowedIn P38719 FINISHED
Object simple assignment target list 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: simple assignment target list | Statement: [Assignment Expressions, notAllowedIn, simple assignment target list]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notAllowedIn
Context triple: [Assignment Expressions, notAllowedIn, simple assignment target list]
  • A. doesNotAllow
    Indicates that one entity prevents, forbids, or does not permit another entity from performing a specific action or being in a certain state.
  • B. isProhibitedFor chosen
    Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
  • C. notAvailableFor
    Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
  • D. notEnforcedBy
    Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing entity.
  • E. notRestrictedBy
    Indicates that something is free from limitations, constraints, or prohibitions imposed by another entity 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_69d6aa81a5d08190aa86689061d1ddd2 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d75117b76c8190b0fb216b1428c3c7 completed April 9, 2026, 7:11 a.m.
PD Predicate disambiguation batch_69d70d2b51448190bae748ed6c23edde completed April 9, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:20 p.m.