Triple
T37186153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pantalica archaeological area |
E921325
|
entity |
| Predicate | hasNecropolisName |
P107125
|
FINISHED |
| Object | North Necropolis |
—
|
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: North Necropolis | Statement: [Pantalica archaeological area, hasNecropolisName, North Necropolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNecropolisName Context triple: [Pantalica archaeological area, hasNecropolisName, North Necropolis]
-
A.
cemeteryName
chosen
Indicates the name assigned to a cemetery associated with an entity.
-
B.
belongsToNecropolis
Indicates that something is part of, contained within, or associated with a particular necropolis.
-
C.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
D.
hasGraveInscription
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
-
E.
hasMortuaryTemple
Indicates that a person, ruler, or deity is associated with or honored by a specific mortuary temple built for their funerary or commemorative purposes.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a008c77d4dc8190b342d7407eaf48fa |
completed | May 10, 2026, 1:47 p.m. |
| PD | Predicate disambiguation | batch_6a008c18531c8190bbe883b73e6d023f |
completed | May 10, 2026, 1:46 p.m. |
Created at: May 3, 2026, 4:15 p.m.