Triple
T13379312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishmar HaGvul |
E319272
|
entity |
| Predicate | hasUnit |
P35
|
FINISHED |
| Object |
Yamas
Yamas is an elite undercover special operations unit of the Israeli Border Police specializing in counterterrorism and covert missions.
|
E1036314
|
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: Yamas | Statement: [Mishmar HaGvul, hasUnit, Yamas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yamas Context triple: [Mishmar HaGvul, hasUnit, Yamas]
-
A.
Yamaka
Yamaka is a canonical text in the Theravāda Abhidhamma that analyzes doctrinal concepts through paired questions and answers to clarify subtle distinctions in Buddhist philosophy.
-
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.
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.
-
D.
Yama
Yama is the historical name of the Russian town now known as Kingisepp, located in Leningrad Oblast near the border with Estonia.
-
E.
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.
- 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: Yamas Triple: [Mishmar HaGvul, hasUnit, Yamas]
Generated description
Yamas is an elite undercover special operations unit of the Israeli Border Police specializing in counterterrorism and covert missions.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Yamas Target entity description: Yamas is an elite undercover special operations unit of the Israeli Border Police specializing in counterterrorism and covert missions.
-
A.
Yamaka
Yamaka is a canonical text in the Theravāda Abhidhamma that analyzes doctrinal concepts through paired questions and answers to clarify subtle distinctions in Buddhist philosophy.
-
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.
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.
-
D.
Yama
Yama is the historical name of the Russian town now known as Kingisepp, located in Leningrad Oblast near the border with Estonia.
-
E.
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.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce56c6c8190adf4e19f6d1bc233 |
completed | April 11, 2026, 11:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f726893a8c8190b26b5f7c7fb96f1f |
completed | May 3, 2026, 10:42 a.m. |
| NEDg | Description generation | batch_69f7276776ec81908769cd9f1cc4707e |
completed | May 3, 2026, 10:45 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69f7280cbb6c819090bee7862e00b900 |
completed | May 3, 2026, 10:48 a.m. |
Created at: April 9, 2026, 9:33 p.m.