Triple
T23630590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebanese independence movement |
E583593
|
entity |
| Predicate | languageOfPoliticalDiscourse |
P105805
|
FINISHED |
| Object | Arabic |
—
|
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: Arabic | Statement: [Lebanese independence movement, languageOfPoliticalDiscourse, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfPoliticalDiscourse Context triple: [Lebanese independence movement, languageOfPoliticalDiscourse, Arabic]
-
A.
languageOfPoliticalContext
chosen
Indicates the language in which a given political context, discourse, or situation is expressed or conducted.
-
B.
languageOfDebate
Indicates that a specified language is the one used for conducting a particular debate.
-
C.
languageOfCampaigning
Indicates the language used to conduct or communicate a campaign (e.g., political, marketing, or advocacy efforts).
-
D.
languageOfPoliticalWork
Indicates the language in which a political work (such as a document, speech, or publication) is expressed or written.
-
E.
usedInPoliticalDiscourse
Indicates that something is employed as a term, concept, or reference within political discussion, debate, or rhetoric.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e7db1c8190aa11ce84fb84d7ef |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:47 p.m.