Triple
T25717503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linky |
E644899
|
entity |
| Predicate | countryWideDeployment |
P67291
|
FINISHED |
| Object | France |
—
|
NE NERFINISHED |
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: France | Statement: [Linky, countryWideDeployment, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryWideDeployment Context triple: [Linky, countryWideDeployment, France]
-
A.
globalDeployment
Indicates that something is deployed, implemented, or made available across multiple countries or worldwide locations.
-
B.
implementedNationwideBy
chosen
Indicates that an initiative, policy, or system has been put into effect across an entire nation by a specified implementing entity.
-
C.
geographicDeployment
Indicates how something is distributed, implemented, or present across different geographic locations or regions.
-
D.
systemStartCountrywide
Indicates that a system-wide operation or service is initiated across the entire country.
-
E.
countryNetwork
Indicates a relationship where countries are connected or associated through some form of shared system, collaboration, or interaction.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 21, 2026, 9:46 p.m.