Triple
T37934086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Orléans e Bragança |
E946297
|
entity |
| Predicate | dynasticSurnameLanguage |
P30275
|
FINISHED |
| Object | Portuguese |
—
|
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 | Statement: [de Orléans e Bragança, dynasticSurnameLanguage, Portuguese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticSurnameLanguage Context triple: [de Orléans e Bragança, dynasticSurnameLanguage, Portuguese]
-
A.
dynasticSurname
Indicates that the two entities share a family name associated with a particular dynasty or ruling lineage.
-
B.
dynasticSurnameAnglicisedAs
Indicates that a dynastic surname has an established or commonly used anglicized form derived from its original language.
-
C.
languageOfDynasty
chosen
Indicates the language or languages predominantly used or associated with a particular dynasty.
-
D.
languageFamilyOfRulers
Indicates the language family historically associated with the rulers of a given political entity or territory.
-
E.
dynasticNameDerivedFrom
Indicates that a dynastic name is derived from, or based on, another name, title, or source.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.