Triple
T20135492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulpudeva |
E491012
|
entity |
| Predicate | earliestPhaseOf |
P15498
|
FINISHED |
| Object | urban history of Plovdiv |
—
|
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: urban history of Plovdiv | Statement: [Pulpudeva, earliestPhaseOf, urban history of Plovdiv]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestPhaseOf Context triple: [Pulpudeva, earliestPhaseOf, urban history of Plovdiv]
-
A.
earliestStage
chosen
Indicates that one entity represents the first or minimum stage, phase, or step in a defined ordered sequence relative to another.
-
B.
earlyPhase
Indicates that the related process, project, or development is in its initial or beginning stage.
-
C.
earliestKnownPeriod
Indicates the earliest historical or temporal period in which the subject is known or documented to have existed, occurred, or been relevant.
-
D.
earliestEpochOf
Indicates the earliest time point or epoch at which a given entity, event, or state first occurs or becomes valid in relation to another.
-
E.
firstPhaseStart
Indicates the point in time when the initial phase of a process or sequence begins.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66766e46c81908721fd47066dc9f8 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.