Triple
T20773092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kopaida |
E511284
|
entity |
| Predicate | wasDrainedInPeriod |
P36222
|
FINISHED |
| Object | late 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: late 19th century | Statement: [Kopaida, wasDrainedInPeriod, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDrainedInPeriod Context triple: [Kopaida, wasDrainedInPeriod, late 19th century]
-
A.
drainedDuring
chosen
Indicates that one entity had its resources, energy, or contents depleted in the course of another event or process.
-
B.
drainedSince
Indicates that one entity has had its contents or resources removed starting from a specific point in time.
-
C.
drainedFor
Indicates that a resource, substance, or energy is removed from one entity for the benefit, use, or purpose of another entity.
-
D.
drainedFrom
Indicates that a substance, resource, or liquid has been removed or emptied out from a particular source or container.
-
E.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c269638881909d96b847f7de5585 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.