Triple
T30128050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pals battalions |
E765753
|
entity |
| Predicate | recruitmentEnded |
P168828
|
FINISHED |
| Object | after introduction of conscription in 1916 |
—
|
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: after introduction of conscription in 1916 | Statement: [Pals battalions, recruitmentEnded, after introduction of conscription in 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitmentEnded Context triple: [Pals battalions, recruitmentEnded, after introduction of conscription in 1916]
-
A.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
B.
hasRecruitStatus
Indicates that an entity holds a particular recruitment-related status or stage within a recruiting process.
-
C.
campaignEnded
Indicates that a previously active campaign has concluded and is no longer ongoing.
-
D.
campaignEndedWith
Indicates that a particular campaign has concluded and specifies the event, condition, or outcome with which it ended.
-
E.
alsoEnded
Indicates that one event or state concluded in addition to another already mentioned event or state.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e4586988190ad89b72dd2af3797 |
completed | May 2, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:14 p.m.