Triple
T25557924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drop Redoubt |
E640624
|
entity |
| Predicate | sawUseDuring |
P4341
|
FINISHED |
| Object | 19th-century coastal defence period |
—
|
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 coastal defence period | Statement: [Drop Redoubt, sawUseDuring, 19th-century coastal defence period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sawUseDuring Context triple: [Drop Redoubt, sawUseDuring, 19th-century coastal defence period]
-
A.
sawServiceDuring
Indicates that one entity experienced or utilized a service during the time period associated with another entity or event.
-
B.
sawActionDuring
Indicates that one entity observed an action or event occurring within a specific time period or during another event.
-
C.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
sawServiceIn
Indicates that an entity observed or experienced a particular service within a specified context, location, or timeframe.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8cb186c819099b247e4a8cbd367 |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 3:44 p.m.