Triple
T2141529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruttians |
E46769
|
entity |
| Predicate | regionNameEtymology |
P21974
|
FINISHED |
| Object | gave name to the region Bruttium |
—
|
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: gave name to the region Bruttium | Statement: [Bruttians, regionNameEtymology, gave name to the region Bruttium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionNameEtymology Context triple: [Bruttians, regionNameEtymology, gave name to the region Bruttium]
-
A.
etymologyRegion
Indicates the geographic region from which a word’s etymological origin or historical linguistic development is derived.
-
B.
seaNameEtymology
Indicates the origin or derivation of the name given to a particular sea.
-
C.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
D.
popularEtymology
Indicates that an etymological explanation is based on common belief or folk interpretation rather than on historically or linguistically accurate origins.
-
E.
regionNamedAfter
chosen
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.