Triple
T20172984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miquèl |
E492013
|
entity |
| Predicate | isNameVariantUsedIn |
P89876
|
FINISHED |
| Object | Romance-language contexts |
—
|
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-language contexts | Statement: [Miquèl, isNameVariantUsedIn, Romance-language contexts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNameVariantUsedIn Context triple: [Miquèl, isNameVariantUsedIn, Romance-language contexts]
-
A.
hasOfficialNameVariant
Indicates that an entity has an alternative official form or version of its name.
-
B.
isSometimesUsedAsVariantOf
chosen
Indicates that one entity is occasionally employed as an alternative or substitute form of another entity, but not as its primary or standard version.
-
C.
hasNameVariantType
Indicates that one name is a specific type or variant of another name, such as an alias, abbreviation, or alternative spelling.
-
D.
hasEthnonymVariant
Indicates that one ethnonym is an alternative or variant form of another ethnonym referring to the same ethnic group.
-
E.
usedInVariant
Indicates that something (such as a component, feature, or element) is utilized or included within a particular variant or version of a larger entity.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66849709c81909b65b421282f9f3b |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:35 p.m.