Triple
T22751100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moro River |
E562698
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Fiume Moro |
—
|
NE NERFINISHED |
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: Fiume Moro | Statement: [Moro River, hasNameInLanguage, Fiume Moro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fiume Moro Context triple: [Moro River, hasNameInLanguage, Fiume Moro]
-
A.
Fiume Moro
chosen
Fiume Moro is the Italian name for the Moro River, a watercourse located in Italy.
-
B.
Fiumana
Fiumana is a small locality in the municipality of Predappio in the Emilia-Romagna region of northern Italy.
-
C.
Fiume
Fiume is the historical name for the Adriatic port city now known as Rijeka, located in present-day Croatia.
-
D.
Fiuminata
Fiuminata is a small municipality in the Marche region of central Italy, known for its mountainous landscape and traditional rural character.
-
E.
Riva River
Riva River is a small river in the Beykoz district of Istanbul, Turkey, known for its scenic natural surroundings and recreational areas along its banks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b9ac348190bff4dc470931f7e3 |
completed | April 29, 2026, 3:23 a.m. |
Created at: April 17, 2026, 3:24 p.m.