Triple
T3731953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lhotshampa |
E79084
|
entity |
| Predicate | facedPolicy |
P42489
|
FINISHED |
| Object | Bhutanese citizenship laws of the 1980s |
—
|
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: Bhutanese citizenship laws of the 1980s | Statement: [Lhotshampa, facedPolicy, Bhutanese citizenship laws of the 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facedPolicy Context triple: [Lhotshampa, facedPolicy, Bhutanese citizenship laws of the 1980s]
-
A.
facedBy
Indicates that one entity is oriented toward and directly opposite another entity, such that it is facing it.
-
B.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
C.
advancedPolicyOf
Indicates that one policy is a more developed, detailed, or progressive version of another policy.
-
D.
targetedByPolicy
chosen
Indicates that an entity is the intended subject or focus of a specific policy’s rules, actions, or effects.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb21002c81908438170ed6f6c271 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.