Triple
T330399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iberian Peninsula |
E6612
|
entity |
| Predicate | languageFamilyDominant |
P11493
|
FINISHED |
| Object | Romance languages |
—
|
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: Romance languages | Statement: [Iberian Peninsula, languageFamilyDominant, Romance languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFamilyDominant Context triple: [Iberian Peninsula, languageFamilyDominant, Romance languages]
-
A.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
B.
languageFamilyCode
Indicates the language family to which a given language belongs, represented by a standardized code.
-
C.
languageOfFamily
Indicates the language or languages commonly used or associated with a particular family.
-
D.
languageFamilyStatus
Indicates the classification or recognition status of a language within a particular language family (e.g., primary, branch, extinct, or disputed).
-
E.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
- F. None of above. chosen
Provenance (4 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eaaeb64881909c7ab9bca3378e2b |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94c6d8881908239d3788c018adf |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea09a5e881908b313cb37409a4f9 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.