Triple
T3272071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France 3 |
E68669
|
entity |
| Predicate | publicServiceMission |
P33202
|
FINISHED |
| Object | regional information |
—
|
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: regional information | Statement: [France 3, publicServiceMission, regional information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicServiceMission Context triple: [France 3, publicServiceMission, regional information]
-
A.
primaryMissionProgram
Indicates that an entity serves as the main or principal program under which another entity’s mission or primary activity is organized or executed.
-
B.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
C.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
D.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
E.
missionField
chosen
Indicates a relationship where an entity’s work, activity, or purpose is directed toward a particular area, domain, or target context as its mission focus.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff6308881908886a44804a0bb09 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.