Triple
T24033723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multinational Force in Lebanon |
E595170
|
entity |
| Predicate | FrenchComponent |
P154591
|
FINISHED |
| Object | French paratrooper units |
—
|
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: French paratrooper units | Statement: [Multinational Force in Lebanon, FrenchComponent, French paratrooper units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrenchComponent Context triple: [Multinational Force in Lebanon, FrenchComponent, French paratrooper units]
-
A.
FrenchForm
Indicates that one entity is a form, version, or expression of another specifically in the French language.
-
B.
isFrancophoneCounterpartOf
Indicates that one entity serves as the French-speaking or French-language equivalent or counterpart of another entity.
-
C.
FrenchRole
Indicates a role or position that an entity holds specifically within a French context (e.g., in France or related to French institutions, culture, or language).
-
D.
FrenchCommander
Indicates that an entity serves as a military commander associated with France.
-
E.
FrenchCouranteCharacteristic
Indicates that something possesses the stylistic or musical features typical of a French courante.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d0ec8081908f98e78944bff040 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 9:56 p.m.