Triple

T8285430
Position Surface form Disambiguated ID Type / Status
Subject Linux Security Modules API E193776 entity
Predicate usedBy P260 FINISHED
Object Yama
Yama is a Linux Security Module that enhances process and ptrace-related security by restricting how processes can inspect or interfere with each other.
 E724151 NE FINISHED

How this triple was built (4 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: Yama | Statement: [Linux Security Modules API, usedBy, Yama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Yama
Context triple: [Linux Security Modules API, usedBy, Yama]
  • A. Yama
    Yama is the Hindu god of death and justice, traditionally regarded as the ruler of the afterlife and judge of the souls of the dead.
  • B. Yamate
    Yamate is a historic hillside district in Yokohama known for its Western-style residences, foreign settlers’ heritage, and scenic views over the city and harbor.
  • C. Sonamura
    Sonamura is a town in the Indian state of Tripura, known as an administrative and commercial center near the India–Bangladesh border.
  • D. Yamadera
    Yamadera is a historic mountainside temple complex in Japan’s Tohoku region, famed for its scenic cliffside halls and panoramic valley views.
  • E. Yahata
    Yahata was a former city in Fukuoka Prefecture, Japan, that became part of the larger city of Kitakyushu through municipal merger.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Yama
Triple: [Linux Security Modules API, usedBy, Yama]
Generated description
Yama is a Linux Security Module that enhances process and ptrace-related security by restricting how processes can inspect or interfere with each other.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Yama
Target entity description: Yama is a Linux Security Module that enhances process and ptrace-related security by restricting how processes can inspect or interfere with each other.
  • A. Yama
    Yama is the Hindu god of death and justice, traditionally regarded as the ruler of the afterlife and judge of the souls of the dead.
  • B. Yamate
    Yamate is a historic hillside district in Yokohama known for its Western-style residences, foreign settlers’ heritage, and scenic views over the city and harbor.
  • C. Sonamura
    Sonamura is a town in the Indian state of Tripura, known as an administrative and commercial center near the India–Bangladesh border.
  • D. Yamadera
    Yamadera is a historic mountainside temple complex in Japan’s Tohoku region, famed for its scenic cliffside halls and panoramic valley views.
  • E. Yahata
    Yahata was a former city in Fukuoka Prefecture, Japan, that became part of the larger city of Kitakyushu through municipal merger.
  • F. None of above. chosen

Provenance (5 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_69ca82e32db481908b72f3804fa71152 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7ad20ae481908179aba245c73fad completed March 31, 2026, 7:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd687e64a08190a45a1cf5f5c32291 completed April 1, 2026, 6:48 p.m.
NEDg Description generation batch_69cd6d55196881909cf5ec925792e09f completed April 1, 2026, 7:09 p.m.
NED2 Entity disambiguation (via description) batch_69cd7e2bdae08190adc51e904e85695e completed April 1, 2026, 8:21 p.m.
Created at: March 30, 2026, 5:52 p.m.