Triple
T4496690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luís |
E100712
|
entity |
| Predicate | IPAInBrazilianPortuguese |
P56903
|
FINISHED |
| Object | /luˈis/ |
—
|
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: /luˈis/ | Statement: [Luís, IPAInBrazilianPortuguese, /luˈis/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IPAInBrazilianPortuguese Context triple: [Luís, IPAInBrazilianPortuguese, /luˈis/]
-
A.
nameInPortuguese
Indicates that an entity is referred to by a specific name when expressed in the Portuguese language.
-
B.
countryNamePortuguese
Indicates the Portuguese-language name assigned to a given country.
-
C.
hasPortugueseNameMeaning
Indicates that an entity has a Portuguese name whose semantic meaning is being specified or referenced.
-
D.
hasOfficialNameInPortuguese
Indicates that an entity has an official name expressed in the Portuguese language.
-
E.
PaulistaDistinction
Indicates a special recognition, status, or honor specifically associated with being from or related to São Paulo (Paulista).
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56bf3ff48190b3aae0136d7fce45 |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1 p.m.