Triple
T11701820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transleithania |
E278144
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | Fiume |
E225516
|
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: Fiume | Statement: [Transleithania, hasComponent, Fiume]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fiume Context triple: [Transleithania, hasComponent, Fiume]
-
A.
Fiume
chosen
Fiume is the historical name for the Adriatic port city now known as Rijeka, located in present-day Croatia.
-
B.
Fiumana
Fiumana is a small locality in the municipality of Predappio in the Emilia-Romagna region of northern Italy.
-
C.
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.
-
D.
Lega River
The Lega River is a watercourse in northeastern Poland that flows through the town of Olecko and forms part of the region’s interconnected lakes and river system.
-
E.
Inva River
The Inva River is a tributary waterway in Russia that feeds into the larger Kama River within the Volga basin.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49a025881909377c81d3debf465 |
completed | April 10, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef834244308190b435e49371d6a6e1 |
completed | April 27, 2026, 3:39 p.m. |
Created at: April 8, 2026, 9:40 p.m.