Triple
T915622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pella, Greece |
E19762
|
entity |
| Predicate | prosperedIn |
P16598
|
FINISHED |
| Object | 4th century BC |
—
|
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: 4th century BC | Statement: [Pella, Greece, prosperedIn, 4th century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prosperedIn Context triple: [Pella, Greece, prosperedIn, 4th century BC]
-
A.
prosperedFrom
Indicates that one entity gained benefit, success, or advantage as a result of another entity, event, or circumstance.
-
B.
historicalPeriodOfProsperity
Indicates a time span in which a society, region, or entity experienced notable economic growth, stability, and overall flourishing.
-
C.
flourishedAmong
Indicates that an entity thrived, prospered, or reached a peak of development within a particular group, environment, or context.
-
D.
richIn
Indicates that something contains a high amount or concentration of a particular substance, quality, or resource.
-
E.
flourishedIn
chosen
Indicates that an entity experienced its peak activity, success, or prominence during a specified time period or era.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b6755c488190b7f7848110e3ea2c |
completed | March 1, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69a4b292d3408190947cbc2f794cf8c5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.