Triple
T5536657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Lebanon Army |
E145177
|
entity |
| Predicate | laterObjective |
P24331
|
FINISHED |
| Object | combat Hezbollah |
—
|
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: combat Hezbollah | Statement: [South Lebanon Army, laterObjective, combat Hezbollah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterObjective Context triple: [South Lebanon Army, laterObjective, combat Hezbollah]
-
A.
laterGoal
chosen
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
B.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
-
C.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
D.
actorObjective
Indicates that an actor has a specific goal, purpose, or intended outcome in relation to another entity or situation.
-
E.
notableObjective
Indicates that an entity has a significant, distinguished, or widely recognized goal, purpose, or target associated with it.
- 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fb07e748190bea74bbde2d7b8ba |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.