Triple
T11702239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riograndenser Hunsrückisch |
E278153
|
entity |
| Predicate | hasContactSituationWith |
P4255
|
FINISHED |
| Object | Portuguese language in Brazil |
—
|
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: Portuguese language in Brazil | Statement: [Riograndenser Hunsrückisch, hasContactSituationWith, Portuguese language in Brazil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactSituationWith Context triple: [Riograndenser Hunsrückisch, hasContactSituationWith, Portuguese language in Brazil]
-
A.
hasContactRole
Indicates that an entity serves in a specific role or capacity as a contact for another entity.
-
B.
hasContactType
Indicates the specific kind or category of contact relationship that exists between two entities.
-
C.
hasKontakion
Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
-
D.
hasContactVariety
Indicates that one entity is associated with a specific type or variety of contact information or communication channel.
-
E.
historicalContactWith
chosen
Indicates that two entities have interacted or been in communication with each other at some point in the past.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49b1080819096593733ee48a187 |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.