Triple
T32730168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger 3 |
E836926
|
entity |
| Predicate | isPlannedToEnterServiceWith |
P106943
|
FINISHED |
| Object | British Army armoured regiments |
—
|
NE NERFINISHED |
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: British Army armoured regiments | Statement: [Challenger 3, isPlannedToEnterServiceWith, British Army armoured regiments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlannedToEnterServiceWith Context triple: [Challenger 3, isPlannedToEnterServiceWith, British Army armoured regiments]
-
A.
plannedEntry
chosen
Indicates that an entity is scheduled or intended to enter another entity, context, or location at a planned future time.
-
B.
isPlannedThrough
Indicates that something is intended to be achieved, organized, or carried out by means of a specified plan, method, or intermediary process.
-
C.
takenIntoServiceAs
Indicates that one entity has been formally accepted, enrolled, or commissioned to perform service or duty for another entity.
-
D.
plannedService
Indicates that a service is scheduled or intended to be provided, but has not yet occurred.
-
E.
plannedUseOf
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:11 a.m.