Triple
T1703633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Appia |
E36820
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Capua |
E44058
|
NE 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: Capua | Statement: [Via Appia, connects, Capua]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Capua Context triple: [Via Appia, connects, Capua]
-
A.
Capua
chosen
Capua is an ancient city in southern Italy that was a prominent center of the Oscan-speaking Samnites and later an important Roman ally and urban hub.
-
B.
Taranto
Taranto is a historic coastal city in southern Italy known as a major naval and commercial hub and for its strategic position on the Gulf of Taranto.
-
C.
Ostia
Ostia was the principal harbor city of ancient Rome, serving as a major commercial and military port at the mouth of the Tiber River.
-
D.
Ligor
Ligor was an important historical port city and regional center on the Malay Peninsula, known for its role in maritime trade and as a strategic outpost in Southeast Asian empires.
-
E.
Salerno
Salerno is a historic port city in southern Italy, known for its strategic role in World War II Allied landings and its position on the Tyrrhenian Sea near the Amalfi Coast.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62f25bac8190977d6f3bd79363cb |
completed | March 6, 2026, 5:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ada0cf5a3481908434c725e85360a2 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 4, 2026, 7:30 p.m.