Triple
T24875593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleutheropolis |
E622558
|
entity |
| Predicate | approximatePeak |
P77981
|
FINISHED |
| Object | 3rd century |
—
|
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: 3rd century | Statement: [Eleutheropolis, approximatePeak, 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePeak Context triple: [Eleutheropolis, approximatePeak, 3rd century]
-
A.
approximateUserPeak
Indicates that one value or event is an estimated or inferred maximum point associated with a particular user.
-
B.
peakApproximateMa
Indicates that one entity’s peak value is approximately equal to another entity’s peak value.
-
C.
areaPeakApprox
Indicates an approximate measurement or estimation of the peak area associated with an entity or event.
-
D.
approximateEstimation
Indicates an estimation relationship where one value or assessment is only roughly or closely, but not exactly, equal to another.
-
E.
hasPeakAround
chosen
Indicates that something exhibits a maximum value, intensity, or prominence in the vicinity of a specified point, range, or condition.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 5:24 a.m.