Triple
T38640674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montone |
E938584
|
entity |
| Predicate | formsRiverSystem |
P1009
|
FINISHED |
| Object | Fiumi Uniti |
—
|
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: Fiumi Uniti | Statement: [Montone, formsRiverSystem, Fiumi Uniti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsRiverSystem Context triple: [Montone, formsRiverSystem, Fiumi Uniti]
-
A.
useRiverSystems
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
-
B.
riverSystem
chosen
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
C.
tributarySystem
Indicates a relationship where one political entity pays regular tribute or offers deference to another, acknowledging the latter’s superior authority or status.
-
D.
riverFormed
Indicates that a river came into existence or was created, typically as a result of natural geological or hydrological processes.
-
E.
raceRiver
Indicates that an entity participates in a race that takes place on or along a river.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:32 p.m.