Triple
T26637780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Britain during the War of the Second Coalition |
E668685
|
entity |
| Predicate | hasInternalEvent |
P6285
|
FINISHED |
| Object | income tax introduction (1799) |
—
|
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: income tax introduction (1799) | Statement: [Great Britain during the War of the Second Coalition, hasInternalEvent, income tax introduction (1799)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternalEvent Context triple: [Great Britain during the War of the Second Coalition, hasInternalEvent, income tax introduction (1799)]
-
A.
hasSideEvent
Indicates that an event is associated with an additional, related side event occurring alongside it.
-
B.
hasSubEvent
chosen
Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
-
C.
hasPrimaryEvent
Indicates that an entity is associated with or linked to its main or most significant event.
-
D.
hasDedicatedEvent
Indicates that a specific event is explicitly organized or reserved for the referenced entity or relationship.
-
E.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 2:28 a.m.