Triple
T15041948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metaurus River |
E378619
|
entity |
| Predicate | hasHistoricalName |
P2834
|
FINISHED |
| Object | Metaurus |
E888547
|
NE 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: Metaurus | Statement: [Metaurus River, hasHistoricalName, Metaurus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Metaurus Context triple: [Metaurus River, hasHistoricalName, Metaurus]
-
A.
Metaurus
chosen
Metaurus is an ancient name for the Metauro River in Italy, known as the site of a decisive battle in the Second Punic War.
-
B.
Curius
Curius is the Roman family name (nomen) associated with the notable statesman and general Manius Curius Dentatus.
-
C.
Ataeniobius
Ataeniobius is a genus of small freshwater killifish within the family Cyprinodontidae.
-
D.
Latreillius
Latreillius is a genus of crustaceans named in honor of the French zoologist and entomologist Pierre André Latreille.
-
E.
Capurrius
Capurrius is a Latinized variant of the Italian surname Capurro, likely used in historical or scholarly contexts.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82f73208190bb55fa6b20074e27 |
completed | April 15, 2026, 12:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fea5b75c04819085996a7f88ab6c38 |
completed | May 9, 2026, 3:10 a.m. |
Created at: April 10, 2026, 3 a.m.