Triple
T14776803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volunteer Force (United Kingdom) |
E347281
|
entity |
| Predicate | inceptionHasCause |
P115746
|
FINISHED |
| Object | 1859 invasion scare |
—
|
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: 1859 invasion scare | Statement: [Volunteer Force (United Kingdom), inceptionHasCause, 1859 invasion scare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionHasCause Context triple: [Volunteer Force (United Kingdom), inceptionHasCause, 1859 invasion scare]
-
A.
inception
Indicates the point in time or event at which something begins, originates, or is first established.
-
B.
inceptionPurpose
Indicates the intended purpose, goal, or function for which something was originally created, initiated, or established.
-
C.
inceptionPart
Indicates that one entity represents a component, segment, or phase within the initial creation or starting process of another entity.
-
D.
inceptionAsSymbol
Indicates that one entity begins to function or be recognized as a symbolic representation or emblem of another entity.
-
E.
inceptionCentury
Indicates the century during which something (such as an institution, tradition, or practice) was originally founded or began.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec817c39081909b08a0ffdfce9936 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:31 a.m.