Triple
T2747356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Methil Docks |
E60899
|
entity |
| Predicate | eraOfPeakActivity |
P18555
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Methil Docks, eraOfPeakActivity, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfPeakActivity Context triple: [Methil Docks, eraOfPeakActivity, 20th century]
-
A.
peakYear
Indicates the year in which something reached its highest or most significant level, performance, or prominence.
-
B.
historicalPeriodOfMajorActivity
chosen
Indicates the historical period during which an entity carried out its most significant or influential activities.
-
C.
refersToEraOfCareer
Indicates that one entity specifies or denotes the particular era or phase within another entity’s career.
-
D.
historicalPeak
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
E.
historicallyActiveIn
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb4ff7b08190b72edb6a2bc5fd19 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.