Triple
T36263599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Leicester |
E892161
|
entity |
| Predicate | reachedUrbanPeak |
P114138
|
FINISHED |
| Object | 2nd century CE |
—
|
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: 2nd century CE | Statement: [Roman Leicester, reachedUrbanPeak, 2nd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedUrbanPeak Context triple: [Roman Leicester, reachedUrbanPeak, 2nd century CE]
-
A.
reachedPeak
chosen
Indicates that an entity has attained its highest or maximum level, value, or performance within a given context or timeframe.
-
B.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
C.
reachesSummitOf
Indicates that one entity successfully arrives at or attains the highest point or summit of another entity.
-
D.
reachedSummitWith
Indicates that one entity arrived at or attained the summit together with another entity, as part of the same ascent or achievement.
-
E.
reachedMaritimePeak
Indicates that an entity has attained its highest level of maritime activity, capability, or dominance within a given context or time period.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b624a9988190871ef23197ec13b2 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.