Triple
T8393474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neapolis |
E197997
|
entity |
| Predicate | foundedAfterDestructionOf |
P81978
|
FINISHED |
| Object | Flavia Neapolis predecessor settlement |
—
|
LITERAL 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: Flavia Neapolis predecessor settlement | Statement: [Neapolis, foundedAfterDestructionOf, Flavia Neapolis predecessor settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAfterDestructionOf Context triple: [Neapolis, foundedAfterDestructionOf, Flavia Neapolis predecessor settlement]
-
A.
foundedAfterDeathOf
Indicates that the founding of one entity occurred only after the death of another entity.
-
B.
foundedAfterArrivalOf
Indicates that one entity was founded only after the arrival or appearance of another specified entity.
-
C.
foundedAfter
Indicates that one entity was founded at a later time than another entity.
-
D.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
E.
foundingOf
Indicates the event or relationship in which an entity is established or created, typically linking the founder(s), the founded entity, and the time or context of its creation.
- F. None of above. chosen
Provenance (4 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8184788081909e9857afff629985 |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:03 p.m.