Triple
T31670729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northumberland Fusiliers |
E808261
|
entity |
| Predicate | enteredBritishService |
P178836
|
FINISHED |
| Object | 1674 |
—
|
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: 1674 | Statement: [Northumberland Fusiliers, enteredBritishService, 1674]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredBritishService Context triple: [Northumberland Fusiliers, enteredBritishService, 1674]
-
A.
enteredNATOService
Indicates that an entity (typically a military asset or unit) began active operational service under NATO command or within NATO forces.
-
B.
enteredRoyalNavyFrontlineService
Indicates that an entity began active duty or operational deployment in the frontline forces of the Royal Navy.
-
C.
enteredUSArmyService
Indicates that an individual began active service in the United States Army at a specific point in time.
-
D.
enteredServiceInNavy
Indicates that an entity began active duty or formal service in a navy on a specified date or during a specified time period.
-
E.
joinedRoyalNavy
Indicates that an individual entered into service as a member of the Royal Navy.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 30, 2026, 11:01 p.m.