Triple
T31887906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magdalene asylums |
E814053
|
entity |
| Predicate | operationalPeriodPeak |
P201216
|
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: [Magdalene asylums, operationalPeriodPeak, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalPeriodPeak Context triple: [Magdalene asylums, operationalPeriodPeak, 19th century]
-
A.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
B.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
C.
operatorAtPeak
Indicates that an operator is present and performing their role at the peak or highest point of a process, structure, or operational cycle.
-
D.
circulationPeakPeriod
Indicates the time period during which circulation (such as distribution or flow) reaches its highest level.
-
E.
isOnPeak
Indicates that one entity is located at, or positioned on, the highest point or summit of another entity.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
| PDg | Predicate description generation | batch_69ffdf46e18c8190a5e4f4e5211cb087 |
completed | May 10, 2026, 1:28 a.m. |
Created at: April 30, 2026, 11:57 p.m.