Triple
T9421349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebanon–United States relations |
E227157
|
entity |
| Predicate | USPolicyGoal |
P677
|
FINISHED |
| Object | support Lebanese sovereignty |
—
|
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: support Lebanese sovereignty | Statement: [Lebanon–United States relations, USPolicyGoal, support Lebanese sovereignty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USPolicyGoal Context triple: [Lebanon–United States relations, USPolicyGoal, support Lebanese sovereignty]
-
A.
nationalGoals
Indicates a relationship where certain objectives or targets are officially set or recognized as the goals of a nation.
-
B.
objectiveOfUnitedStates
chosen
Indicates that something is an official objective or goal pursued by the United States.
-
C.
hasPolicyGoal
Indicates that an entity is associated with, or aims to achieve, a specific policy objective or target.
-
D.
policyAim
Indicates that a policy is intended to achieve, promote, or be directed toward a particular goal or objective.
-
E.
politicalGoal
Indicates a relationship where an entity aims to achieve, promote, or realize a specific political outcome, policy, or state of affairs.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c2651c48190808281779fab49df |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.