Triple
T9290005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fernandes |
E223491
|
entity |
| Predicate | hasOrthographicAccent |
P32687
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Fernandes, hasOrthographicAccent, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrthographicAccent Context triple: [Fernandes, hasOrthographicAccent, no]
-
A.
hasAccent
Indicates that an entity speaks with or possesses a particular accent or distinctive pronunciation style.
-
B.
hasOrthographicConvention
Indicates that there is a specific writing or spelling convention that governs how something is represented in written form.
-
C.
hasOrthographicReform
Indicates that an entity has undergone or is associated with a change or standardization in its writing system or spelling conventions.
-
D.
accentedFormOf
chosen
Indicates that one linguistic form is an accented or diacritically marked variant of another, more basic form.
-
E.
hasOrthographyStatus
Indicates the orthographic status or condition of how something is written or spelled, such as its conformity to a particular writing system or standard.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08643a848190a8b5be1ccc0b2ef6 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.