Triple
T27257657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Anad |
E687669
|
entity |
| Predicate | hasBeenControlledBy |
P5058
|
FINISHED |
| Object | Houthi forces |
—
|
NE NERFINISHED |
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: Houthi forces | Statement: [Al Anad, hasBeenControlledBy, Houthi forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenControlledBy Context triple: [Al Anad, hasBeenControlledBy, Houthi forces]
-
A.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
B.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
-
C.
exertsControlOver
Indicates that one entity has the power or authority to direct, influence, or determine the actions or decisions of another entity.
-
D.
lifetimeControlledBy
Indicates that the existence or duration of one entity is dependent on and ends with the controlling entity’s lifetime.
-
E.
historicallyControlledBy
chosen
Indicates that an entity was under the control, rule, or governance of another entity during some period in the past.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 10:50 a.m.