Triple
T10637503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAEOA |
E250629
|
entity |
| Predicate | usesLegalNameLanguage |
P15
|
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: [RAEOA, usesLegalNameLanguage, Portuguese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLegalNameLanguage Context triple: [RAEOA, usesLegalNameLanguage, Portuguese]
-
A.
translationOfLegalName
Indicates that one name is a translated version of another entity’s official legal name.
-
B.
hasFullNameLanguage
Indicates that the language in which a full name is expressed is associated with that full name.
-
C.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
D.
canBeLegalGivenName
Indicates that a given name satisfies the rules or conditions required to be considered legally valid.
-
E.
languageOfWorkOrName
chosen
Indicates the language in which a work is created or a name is expressed.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfae51148190840a4e52b29ad06e |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:04 p.m.