Triple
T21516557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebanese Forces |
E530857
|
entity |
| Predicate | bannedPeriod |
P134351
|
FINISHED |
| Object | 1994–2005 |
—
|
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: 1994–2005 | Statement: [Lebanese Forces, bannedPeriod, 1994–2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bannedPeriod Context triple: [Lebanese Forces, bannedPeriod, 1994–2005]
-
A.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
B.
wasBannedDuring
chosen
Indicates that an entity was prohibited or barred from participation or access for the duration of a specified time period or event.
-
C.
banPeriodStart
Indicates the date or time at which a ban or prohibition begins to take effect.
-
D.
banPeriodEnd
Indicates the point in time when a ban or prohibition on an entity or action is scheduled to end.
-
E.
bannedBy
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee81416f288190a62f62ddd6895b24 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.