Triple
T3272067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France 3 |
E68669
|
entity |
| Predicate | hasRegionalEditions |
P32680
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [France 3, hasRegionalEditions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalEditions Context triple: [France 3, hasRegionalEditions, yes]
-
A.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
B.
hasRegionalVariationsIn
chosen
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
-
C.
hasInternationalVersion
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
-
D.
regionalVariantOf
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
-
E.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
- 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.