Triple
T21647598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLNC-Union des Combattants |
E534259
|
entity |
| Predicate | languageOfCommuniques |
P33549
|
FINISHED |
| Object | French |
—
|
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 | Statement: [FLNC-Union des Combattants, languageOfCommuniques, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCommuniques Context triple: [FLNC-Union des Combattants, languageOfCommuniques, French]
-
A.
languageOfCommunications
chosen
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
B.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
C.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
D.
languageOfOfficialReports
Indicates the language in which an entity’s official reports are written or issued.
-
E.
languageOfUnion
Indicates that a specified language is officially used or recognized as a language of a particular union or union-level 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef59124e1c81908d454894d66359e7 |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.