Triple
T28106014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London fog |
E710363
|
entity |
| Predicate | wasCommonInPeriod |
P32297
|
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: [London fog, wasCommonInPeriod, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCommonInPeriod Context triple: [London fog, wasCommonInPeriod, 19th century]
-
A.
commonInPeriod
chosen
Indicates that something frequently occurs, appears, or is prevalent during a specified time period.
-
B.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
C.
usedDuringEraOf
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
-
D.
appearsInTimePeriod
Indicates that an entity is present, active, or occurs within a specified time period.
-
E.
firstWidelyUsedDuring
Indicates that something (such as a concept, technology, or practice) came into its first period of broad or widespread use during a specified time or era.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64095680c8190a220f9345db8688d |
completed | May 2, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:08 p.m.