Triple
T12316523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | March 14 Alliance |
E293613
|
entity |
| Predicate | positionOnWeapons |
P104433
|
FINISHED |
| Object | called for Hezbollah disarmament |
—
|
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: called for Hezbollah disarmament | Statement: [March 14 Alliance, positionOnWeapons, called for Hezbollah disarmament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnWeapons Context triple: [March 14 Alliance, positionOnWeapons, called for Hezbollah disarmament]
-
A.
weaponMount
Indicates that one entity serves as a mounting point or support structure for attaching or holding a weapon on another entity.
-
B.
positionInArms
Indicates that one entity is being held or carried within the arms of another entity.
-
C.
swordPosition
Indicates the spatial location or placement of a sword relative to a reference point or entity.
-
D.
weaponControl
Indicates that one entity has authority over, access to, or the ability to direct the use of a weapon associated with another entity.
-
E.
positionOnInstruments
Indicates the specific role or seat an individual holds within a group of instruments, such as in an orchestra or ensemble.
- F. None of above. chosen
Provenance (4 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.