Triple
T28793769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confluentes |
E727029
|
entity |
| Predicate | hasAlternativeModernSpelling |
P457
|
FINISHED |
| Object | Confluentia |
—
|
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: Confluentia | Statement: [Confluentes, hasAlternativeModernSpelling, Confluentia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeModernSpelling Context triple: [Confluentes, hasAlternativeModernSpelling, Confluentia]
-
A.
hasAlternativeToponymy
Indicates that an entity is associated with one or more alternative place names or toponyms used to refer to the same geographic location.
-
B.
hasVariantSpelling
chosen
Indicates that one term is an alternative spelling form of another term.
-
C.
isModernFormOf
Indicates that one entity is a newer or contemporary version, adaptation, or evolution of another earlier entity.
-
D.
hasAlternativeVocalization
Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
-
E.
hasModernStandardForms
Indicates that an entity possesses one or more contemporary, standardized versions or representations of itself.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 6:24 a.m.