Triple
T37071707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faversham Creek |
E917598
|
entity |
| Predicate | historicalPeriodOfPeakUse |
P122700
|
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: [Faversham Creek, historicalPeriodOfPeakUse, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfPeakUse Context triple: [Faversham Creek, historicalPeriodOfPeakUse, 19th century]
-
A.
historicalPeriodOfGreatestUse
chosen
Indicates the time period during which something was used most intensively or prevalently.
-
B.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
C.
historicalPeriodOfNotableUse
Indicates the historical time period during which the entity was notably or most prominently used.
-
D.
historicalPeakIndustrialPeriod
Indicates the time period during which an entity reached its highest level of industrial activity or development.
-
E.
historicalPeriodOfFirstUse
Indicates the historical time period during which something was first used or came into use.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a017bc21b048190b9c680013de203b6 |
completed | May 11, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_6a017aa09c4481909c3b55e0cd13501e |
completed | May 11, 2026, 6:43 a.m. |
Created at: May 3, 2026, 4:14 p.m.