Triple
T1602223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chat Moss |
E34417
|
entity |
| Predicate | drainedSince |
P30644
|
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: [Chat Moss, drainedSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainedSince Context triple: [Chat Moss, drainedSince, 19th century]
-
A.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
B.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
C.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
D.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
-
E.
minedSince
Indicates that a resource or material has been extracted from a location continuously starting from a specified point in time.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a95aada3f881909053363c01de8b57 |
completed | March 5, 2026, 10:29 a.m. |
Created at: March 4, 2026, 7:28 p.m.