Triple
T25520248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichskreise |
E639624
|
entity |
| Predicate | hasNumberAtPeak |
P165818
|
FINISHED |
| Object | 10 imperial circles |
—
|
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: 10 imperial circles | Statement: [Reichskreise, hasNumberAtPeak, 10 imperial circles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberAtPeak Context triple: [Reichskreise, hasNumberAtPeak, 10 imperial circles]
-
A.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
B.
hasNumberOfSeatsAtPeak
Indicates the maximum number of seats available or occupied at the peak usage or capacity of something.
-
C.
hasPeakOver
Indicates that one entity’s peak (such as a maximum value, height, or intensity) exceeds that of another entity.
-
D.
hasPeakCount
Indicates the number of distinct peaks associated with an entity.
-
E.
reachedPeak
Indicates that an entity has attained its highest or maximum level, value, or performance within a given context or timeframe.
- F. None of above. chosen
Provenance (4 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 21, 2026, 2:59 p.m.