Triple
T18758713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severan Bridge at Cendere |
E458714
|
entity |
| Predicate | dedicatedTo |
P500
|
FINISHED |
| Object | Geta |
—
|
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: Geta | Statement: [Severan Bridge at Cendere, dedicatedTo, Geta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Geta Context triple: [Severan Bridge at Cendere, dedicatedTo, Geta]
-
A.
Geta
chosen
Geta was a short-reigning Roman emperor of the Severan dynasty, known for his joint rule and bitter rivalry with his brother Caracalla, who ultimately had him murdered.
-
B.
Geta Bera
Geta Bera is a traditional Sri Lankan drum central to Kandyan dance performances, known for its distinctive shape and rhythmic patterns.
-
C.
Enyō
Enyō is a minor Greek goddess associated with war, destruction, and the bloody chaos of battle, often depicted as a companion of Ares.
-
D.
Sadanaru
Sadanaru is a Japanese given name historically borne by members of the imperial family, including Prince Fushimi Sadanaru.
-
E.
Seishirō
Seishirō is a Japanese given name commonly used for male individuals.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579f42d0881909bd9ca9c7916516a |
completed | April 20, 2026, 12:57 a.m. |
Created at: April 10, 2026, 11:52 a.m.