Triple
T26012238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suamox |
E646930
|
entity |
| Predicate | modernSuccessorSite |
P88073
|
FINISHED |
| Object | Sogamoso |
—
|
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: Sogamoso | Statement: [Suamox, modernSuccessorSite, Sogamoso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSuccessorSite Context triple: [Suamox, modernSuccessorSite, Sogamoso]
-
A.
successorSite
Indicates that one site directly follows and replaces another site in a sequence or evolution of sites.
-
B.
modernSiteCorrespondsTo
chosen
Indicates that a present-day site occupies, aligns with, or directly relates to the location or extent of another (typically historical or earlier) site.
-
C.
successorStateSite
Indicates that one site or state of a site directly follows another as its immediate successor in a sequence or process.
-
D.
successorUseOfSite
Indicates that one use or function of a site directly follows and replaces a previous use of that same site in time.
-
E.
modernStateSuccessor
Indicates that one modern state is the legal, political, or historical successor to another earlier state.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 22, 2026, 9:02 a.m.