Triple
T23980535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernadotte dynasty |
E604494
|
entity |
| Predicate | founderCountryOfOrigin |
P42058
|
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: [Bernadotte dynasty, founderCountryOfOrigin, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderCountryOfOrigin Context triple: [Bernadotte dynasty, founderCountryOfOrigin, France]
-
A.
founderNationality
Indicates that the specified person’s country of origin or citizenship is the one associated with the founder in question.
-
B.
foundingLocationPresentCountry
Indicates the present-day country in which the location where something (typically an organization or institution) was founded is situated.
-
C.
founderBirthPlace
Indicates the place where the founder of an entity was born.
-
D.
foundersOrigin
chosen
Indicates that the relationship specifies the geographic or cultural origin of the founders of an entity.
-
E.
foundedCompanyInCountry
Indicates that an entity established or created a company whose founding took place within a specified country.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2bd58448190a64e7a9020109229 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:27 p.m.