Triple
T24973814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fens |
E624962
|
entity |
| Predicate | majorDrainagePhase |
P161430
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Fens, majorDrainagePhase, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorDrainagePhase Context triple: [Fens, majorDrainagePhase, 17th century]
-
A.
majorDrainageFor
Indicates that one watercourse or drainage feature serves as the primary outlet or drainage system for another area or hydrologic feature.
-
B.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
-
C.
mainPhase
Indicates that an event, action, or state occurs during the primary or central phase of a larger process or sequence.
-
D.
majorUnificationPhase
Indicates a significant stage in which previously separate elements, systems, or groups are brought together into a more unified whole.
-
E.
majorBreakupPhase
Indicates a stage in which a significant romantic relationship has ended or is actively dissolving, often involving emotional, social, and practical separation between the partners.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 18, 2026, 6:01 a.m.