Triple
T5685214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pylos |
E125295
|
entity |
| Predicate | hasModernCounterpart |
P32013
|
FINISHED |
| Object | modern town of Pylos |
—
|
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: modern town of Pylos | Statement: [Pylos, hasModernCounterpart, modern town of Pylos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernCounterpart Context triple: [Pylos, hasModernCounterpart, modern town of Pylos]
-
A.
hasModernSuccessor
chosen
Indicates that an entity is followed or replaced by another entity that serves as its modern equivalent or continuation.
-
B.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
C.
hasCounterpart
Indicates that one entity corresponds to, matches, or serves as an equivalent or parallel version of another entity.
-
D.
modernEquivalent
Indicates that one entity serves as the contemporary or updated counterpart of another earlier or traditional entity.
-
E.
hasModernFormulationIn
Indicates that something has a contemporary or updated version expressed or formulated within a specified context, framework, or medium.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.