Triple
T11663133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribeiro |
E277171
|
entity |
| Predicate | wordTypeOfOrigin |
P2530
|
FINISHED |
| Object | topographic term |
—
|
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: topographic term | Statement: [Ribeiro, wordTypeOfOrigin, topographic term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wordTypeOfOrigin Context triple: [Ribeiro, wordTypeOfOrigin, topographic term]
-
A.
etymologyType
chosen
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
B.
etymologicalSource
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
-
C.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
D.
etymologicalRole
Indicates the specific function or contribution an element has within the historical origin and development of a word or term.
-
E.
etymologyTheme
Indicates that something (such as a word, name, or term) has its origin, derivation, or linguistic history related to a particular theme, source, or conceptual basis.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d3a64c819099f398ea22c8c180 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.