Triple
T34772322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clyde, Scotland |
E1002395
|
entity |
| Predicate | hasHistoricalPeriodOfPeak |
P55472
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Clyde, Scotland, hasHistoricalPeriodOfPeak, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalPeriodOfPeak Context triple: [Clyde, Scotland, hasHistoricalPeriodOfPeak, 19th century]
-
A.
historicalPeak
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
B.
hadPeakInfluencePeriod
chosen
Indicates the time span during which an entity exerted its greatest or most significant influence.
-
C.
hasHistoricalEraOfGrowth
Indicates a period in which the subject experienced notable development, expansion, or progress in its history.
-
D.
hasPeakOccasion
Indicates that something reaches its highest or most significant level, intensity, or occurrence during a particular occasion or event.
-
E.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: May 3, 2026, 3:59 p.m.