Triple
T16543710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmonie Mutuelle Semi de Paris |
E401885
|
entity |
| Predicate | languageOfEventInformation |
P15031
|
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: [Harmonie Mutuelle Semi de Paris, languageOfEventInformation, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfEventInformation Context triple: [Harmonie Mutuelle Semi de Paris, languageOfEventInformation, French]
-
A.
languageOfEvent
chosen
Indicates the language in which an event is conducted, presented, or communicated.
-
B.
languageOfVenue
Indicates the language primarily used or officially designated for communication at a given venue.
-
C.
languageOfOrganizer
Indicates the language used by the organizer in conducting or presenting the associated event or activity.
-
D.
languageOfInformationCenter
Indicates the language in which an information center communicates or provides its information resources.
-
E.
languageOfLocalOrganisingCommittee
Indicates the language used by the local organising committee to conduct its activities, communication, and official documentation.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3455fab34819086c77ff45b85f5db |
completed | April 18, 2026, 8:48 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.