Triple
T24785533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivers of London |
E620106
|
entity |
| Predicate | alsoKnownAsRegion |
P112037
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Rivers of London, alsoKnownAsRegion, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoKnownAsRegion Context triple: [Rivers of London, alsoKnownAsRegion, United States]
-
A.
regionallyKnownAs
Indicates that an entity is known by a particular name or designation within a specific geographic region.
-
B.
regionAlsoCalled
chosen
Indicates that a geographic or administrative region is known by an alternative name or alias.
-
C.
isRegionalAlternativeTo
Indicates that one entity serves as a counterpart or substitute for another within a specific geographic region or local context.
-
D.
regionalVariantOf
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
-
E.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:45 a.m.