Triple
T9793333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenoutean corpus |
E237657
|
entity |
| Predicate | centeredOn |
P164
|
FINISHED |
| Object | Atripe |
E237654
|
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: Atripe | Statement: [Shenoutean corpus, centeredOn, Atripe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Atripe Context triple: [Shenoutean corpus, centeredOn, Atripe]
-
A.
Atripé
chosen
Atripé was an ancient Egyptian town in Upper Egypt notable as the home of the influential Coptic monastic leader Shenoute.
-
B.
Atril
Atril is a lightweight document viewer, primarily for PDF and PostScript files, used as part of the MATE desktop environment.
-
C.
Atripalda
Atripalda is a historic town in southern Italy’s Campania region, known for its archaeological remains and proximity to the city of Avellino.
-
D.
Apenrade
Apenrade is a historic coastal town in southern Denmark, known today by its Danish name Aabenraa and situated near the German border.
-
E.
Atabillos
Atabillos is a noble title namesake, likely referring to a historical place, family, or lineage associated with the Marquess of the Atabillos.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda346945481908c2698a79c578ef5 |
completed | April 1, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc5118a481908a65d730f86c7723 |
completed | April 5, 2026, 2:43 a.m. |
Created at: March 30, 2026, 8:28 p.m.