Triple
T27903169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wat's Dyke |
E705690
|
entity |
| Predicate | purposeHypothesis |
P14769
|
FINISHED |
| Object | military defense |
—
|
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: military defense | Statement: [Wat's Dyke, purposeHypothesis, military defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeHypothesis Context triple: [Wat's Dyke, purposeHypothesis, military defense]
-
A.
hypothesis
Indicates that a statement or proposition is tentatively assumed to be true and is subject to testing, evaluation, or proof.
-
B.
proposesHypothesis
Indicates that one entity puts forward a tentative explanation or hypothesis for consideration regarding another entity or phenomenon.
-
C.
exploresHypothesis
Indicates that an entity actively investigates, tests, or examines a proposed hypothesis to understand its validity or implications.
-
D.
purpose
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
E.
functionHypothesis
chosen
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:43 p.m.